Develop Bugs

Rhobuntu: Ubuntu 9.04 and Debian (test) UPDATE [19/09/2010]

Important - Read First!
First of all you must know that everything you do is on your own risk. Your device was not designed to run GNU/Linux or Android and that's why you shouldn't expect everything to be perfectly safe. If you don't want any troubles then simply don't tamper with your phone. On the other hand, installing Rhobuntu is probably less dangerous than installing alternative ROM's, because it doesn't touch your ROM and runs completely from the SD card. If something goes wrong and the system would hang up, you always can remove the battery and boot into Windows Mobile. Still, we can't guarantee you anything and we won't be liable for any damage that might happen to your device. If you don't accept this, don't install Rhobuntu.
At the moment two problems are known to occur when using Rhobuntu. They are, however, not Rhobuntu specific and may also occur when using Android.
1- After booting back into WinMo, you can't install or run unsigned apps. This problem probably has something to do with the way haret kicks WinMo out of the RAM. It also seems to occur only in combination with the use of Exchange Server. The only known solution at the moment is Hard Reset. Some users also reported that it can be fixed by using Visual Studio 2008. Check out this threads:
o Not digitally signed with a Trusted certificate/ Activesync keeps UNINSTALLING!
o Program... is not digitally signed with trusted certificate. HELP!
2- Since we still have no proper battery charge indicator working, you might not notice that your battery is completely drained. Deep discharge is, however, not good for batteries and may in some cases even damage them. Here is a thread dealing with this problem when running Android
o Android killed my USB connection, please help
The majority of Rhobuntu users doesn't face these problems, but just in case, you've been warned.
WIKI http://wiki.xda-developers.com/index.php?pagename=RhodiumUbuntu
WEBSITE https://sites.google.com/site/rhobuntu/
This build by Walter79 and the Rhobuntu team:
Rhobuntu 9.04 19.09.2010
changelog:
- zimage update (Xandroid Build 16/09)
- sphone 0.04 (thanks AmiPro)
- 3G scripts update (thanks AmiPro)
- sound works partial (thanks to phhuson) !!! run /sdcard/ubuntu/playwav2 after boot !!!
- alsaplayer added
Download:
Link1: http://www.megaupload.com/?f=RWDJWUN0
Link2: http://rhobuntu.4shared.com
Debian Squeeze Test 19.09.2010
For more information please look at this post http://forum.xda-developers.com/showpost.php?p=8186181&postcount=1208
Download:
link1: http://www.4shared.com/dir/n-2ObqP_/pro2-debian.html
Old Build (27/06/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (13/05/2010)
*http://www.megaupload.com/?f=RWDJWUN0
*http://rhobuntu.4shared.com
Old Build (14/04/2010)
*part one:http://rapidshare.com/files/375930803/Jaunty_14_04_2010.7z.001 MD5 77430e728bb17277e671cc55ae03161f and part two: http://rapidshare.com/files/375939439/Jaunty_14_04_2010.7z.002 MD5 523589000dcd5d1dcea668bbe51253af
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (11/04/2010)
* http://rs427.rapidshare.com/files/374730149/Jaunty_11_04_2010.7z
* http://rhobuntu.4shared.com
* http://www.megaupload.com/?f=RWDJWUN0
Old Build (10/04/2010)
*http://rapidshare.com/files/374138895/Jaunty_10_04_2010.7z
*http://rhobuntu.4shared.com

Pretty cool idea, keep us posted!

Definitely an awesome idea, and one I had been thinking about myself since my original Touch Pro days. An embedded version of Linux should run great on these devices. Hopefully momentum will grow surrounding this.

thats very interesting. any pictures of this running? maybe things can be pulled from android.

THANKS!!!! downloading now!

tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.

aq3e said:
tried it on my Touch Pro 2 (AT&T Tilt2), No luck. Started to boot, Complained about /etc/init then poof reboot after 7 seconds. Am I missing something.
Click to expand...
Click to collapse
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?

Help!
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.

dicko99 said:
I extracted all the files on to a newly formatted 2GB card.
Ran haret and everything ran fine. Bit 'interesting' navigating round the screen but got there in the end.
However, since rebooting my phone back into WM I cannot run any unsigned programs such as haret that worked fine before.
The error says "The file blah cannot be opened either it is not signed with a trusted certificate..."
Any idea what's changed and how I can get my phone back to how it was?
R.
Click to expand...
Click to collapse
Wierd, my winmo works find, minus the calibration issue, it's brilliant, we need some linux Devs to look into this. as a windows user, i have no idea on what to do
Thanks (All we need now is win XP )
Badwolve1

I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.

dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
did you install anything recently, could try uninstalling it

dicko99 said:
I think something got corrupted/overwritten on my phone...
I cannot run any unsigned apps whether they are installed on the storage card or internal memory.
I cannot even install new apps! When I run the cab file, I get the usual "This program is from an unknown publisher..." and when I select yes for continue it immediately comes up with "Installation of blah was unsuccessful."
Time for a hard reset? I'd really prefer not to if anyone can suggest a better way of getting back to how it was.
R.
Click to expand...
Click to collapse
try installing SdkCerts.cab
http://forum.xda-developers.com/showthread.php?t=554240
the cab is included with the rhodium keymapper zip file. (keymapper app is worth installing as well )

sdkcerts won't install. It has the same problem as other cabs where it prompts to say the program is from an unknown publisher and when I tap Yes to continue it still fails with "Installation of SdkCerts.CAB was unsuccessful."

Tried booting it up on my Verizon TP2 and all it does is run haret and then freeze.

Thanks for putting this together, sebbo90. It boots nicely, and actually performs quite well on my Tilt2. I hope some of the developers take notice of this project and consider fixing the major usability issues like the front keys and the display calibration.

After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.

spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
How did you even get it to boot?
EDIT: Do you think it will not boot for me since you all are using GSM and i am using a CDMA phone? Some settings may need to be changed i guess. I have been messing around but no luck.

spdweb said:
After the first boot I cant get the GUI to run anymore. Removing the directory from the SD and uploading a fresh copy fixes it for one boot only. After that it just hangs at command line.
Click to expand...
Click to collapse
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps

sebbo90 said:
Did you change the mtype in the sartup script to the tilt2, the one i used is set for the rhod100, i hope that helps. Is anyone else's not working btw?
Click to expand...
Click to collapse
If the mtype needs to be changed, what should it be instead of the default 2292, forgive my ignorance.
EDIT: must be a fluke, it booted now, did not change a thing. Re-extracted the ubuntu rar and shoved it back on the SD and booted. Great Job. All we need now is calibration to get started.

sebbo90 said:
I had this problem what i did to fix it was to was to do a full reformat on my sd card (not a quick one) this then helped and now it boots everytime. Hope this helps
Click to expand...
Click to collapse
I got it working now. It was the directory structure I was using. I spent about 2 hours last night working on the calibration issue. If I could get that working it would be sweet. Tried a newer version of haret and tweaked the startup.txt a bit but the calibration still goes out of range.
On a brighter note, the calibration works fine when booting xdandroid with haret though it is a manual calibration there is hope anyway.

"r2: Superboot" not working

Tried to post this in the developers forum in the correct thread but I'm restricted - sorry mods but if you could move this post, that would be ace?
I've tried following the instructions for using the r2: Superboot process to root my phone, but having trouble with it.
I've installed the drivers that came in the zip - with the phone switched on as normal, Windows recognises it no problem, as does ADB. When I put the phone into the bootloader, Windows doesn't recognise it - showing in device manager as "Android 1.0" and making a funny beep as the USB is plugged in. Neither ADB or Fastboot recognise the phone as being attatched.
Just bought the phone today, sim free, in the UK, so possibly a different hardware or software version to those who've got it working?
When running normally, "About Phone" shows as Android version 4.0.1, Kernel 3.0.1-ge2433f2 [email protected] #1 and Build number ITL41D.
In the bootloader it shows Fastboot Mode, Product Name - tuna, Varient - magura, HW Version 9, Bootloader Version - PRIMEKJ10, Signing - production, Lock State - locked.
Anyone got any ideas where to go from here?
Thanks

Make sure you turn on ADB Debugging from the settings menu and plug it into your pc.
Then run:
adb devices
See if its there. If so, continue

You need to force the drivers to install in fastboot mode first. Download the 'drivers' files from *THIS* forum and try them it worked for me (make sure you are in fastboot mode when you install them). You will also need to unlock the bootloader first which will wipe your phone including sdcard so make sure you have any files you need backed up first.
Mark.

Ah, fella, you're a superstar!
Done it now, can tweak my phone just how I want it now.
Thanks so much for your help

mskip said:
You will also need to unlock the bootloader first which will wipe your phone including sdcard so make sure you have any files you need backed up first.
Mark.
Click to expand...
Click to collapse
I have been assuming that 'wipe your phone' means wipe it of anything the user has put on it, but that the OS remains; is that correct?

Yeh, it resets it to the same state as when you first get the phone, wiping any personal data and any changes you've made to the system
Have to say I'm impressed though, it remembered by Wifi password and downloaded all my apps again without me doing anything! I'm liking ICS so far!

scooby359 said:
Yeh, it resets it to the same state as when you first get the phone, wiping any personal data and any changes you've made to the system
Have to say I'm impressed though, it remembered by Wifi password and downloaded all my apps again without me doing anything! I'm liking ICS so far!
Click to expand...
Click to collapse
The Wifi password and app restoration is all in the cloud just pointing that out lol

scooby359 said:
Yeh, it resets it to the same state as when you first get the phone, wiping any personal data and any changes you've made to the system
Have to say I'm impressed though, it remembered by Wifi password and downloaded all my apps again without me doing anything! I'm liking ICS so far!
Click to expand...
Click to collapse
Your passwords and all your list of apps from the market are stored under your google account so when you sign back in on a new phone (or wiped one) and synch with your phone all your market apps under that account are re-downloaded and certain information is restored.
Mark.

I don't remember that happening on my old Desire.. that just something I've missed or new to ICS?
I've noticed ICS brings up my bookmarks from Chrome on my PC, that's deffinately a new trick!

scooby359 said:
I don't remember that happening on my old Desire.. that just something I've missed or new to ICS?
I've noticed ICS brings up my bookmarks from Chrome on my PC, that's deffinately a new trick!
Click to expand...
Click to collapse
Could be you didn't enable personal data backup, or Sense doesn't do that (my guess)
And the Chrome bookmark sync is one of the things I'm definitely looking forward to with ICS I know I can do it with some apps right now but having features be native is always nice

Internal SDcard Busted, Can't Format or Write (Forever Locked as Read-only)

HI,
I used to be more active in this forum, but honestly nowadays I can't found any reason to since everything has been smooth sailing for me without any problems—until this day, at least. Somehow I got my internal sdcard busted, it was pretty spontaneous, all I can recall is suddenly the system starts to reboot itself. Nothing much, I thought to myself, problem is the system keeps rebooting, it doesn't even last a minute. Naturally when faced with this problem one would do the usual procedure, namely completely format the thing to stock the rule out any possibility on the user side of things, but then this is the part when it starts to get interesting...
The thing refused to be formatted, seriously, it baffles me at first but it does
Things I've tried:
Fastboot, it hangs at writing system, whether I was doing it line per line manually or via the flash_all.sh script, I haven't tried the toolkit but I think it's safe to assume that It'll do the same thing. Even if it does go on (which it did, once) it doesn't do any sort of changes whatsoever to the system.
ADB, nope, not this one either. And since the system reboots faster before I can do anything worthwhile it's pretty much out of the question.
Recovery, multiple times I've tried nuking everything via CWM, nada. I've tried TWRP too, I have to boot it from fastboot since it apparently doesn't allow me to flash a new recovery either, it reverts back to CWM every time. Also tried to flash a different ROM (CM), that didn't work, it spits out an error message regarding some failure in changing metadata, thought it was a corrupted file or something, so I re-downloaded it, that doesn't work. Still convinced that it's corrupted I tried 4 different version of it without any luck. Even the one I had successfully flashed before. Interestingly enough, flashing the exact same ROM I'm currently using (ShinyROM) works, not that it seems to do anything.
Built-in data format from settings, now this doesn't work because I assume that it needs the stock recovery to work, which I couldn't flash because it wouldn't let me—in a sense that it flashes just fine on the command line—fastboot doesn't show up any error or anything—but it defaults back to CWM as soon as I reboot it.
Manually via terminal emulator/file manager, still nothing, curiously enough, Terminal Emulator indicates that the whole system is read-only (I tried making a file with it, it shows that exact message).
Grit my teeth, clench my fist and screams out every curse word that I know of, this somewhat reduced my stress levels, but ultimately yields nothing.
Which led to be believe that either my phone was either a) Haunted or b) Has a serious hardware problem, I'm leaning on the latter. A few quick lookup with my limited amount of Google-fu and I've found several threads that described the exact same issue:
http://forums.androidcentral.com/go...-factory-settings-no-matter-method-i-try.html
http://forums.androidcentral.com/go...eset-nexus-7-2102-using-multiple-methods.html
Both of which hints at it being a hardware problem. Which was my biggest fear since I can't really revert the phone back to stock now can I? Locking the bootloader doesn't seem to work either (the 'fastboot oem lock' command works just fine but just like every single thing I've tried, reverts back to my previous setup as soon as I did a reboot), plus this means I have to send it back with my private data still on it, and I can't say I trust Samsung, Google (or anyone really) with my private data. Not to mention some of the stories I've heard/read about Samsung and their policy regarding rooted devices (much less ones with an unlocked bootloader).
In case it helps, here's a few more details:
What state the device is currently in:
It boots up just fine, but nor for long, apps starts to hang and ends up with a cold reboot (sorry if it's not the right jargon, but it starts right from the Google screen).
Everything that doesn't require you to access the filesystem works fine.
Apps doesn't seem to be able to write anything to the filesystem, I tried backing it up with Titanium Backup, much to my surprise the backup files weren't made (although TiBu seems to indicate that they were).
What the device is running:
Variant: Maguro 16GB
ROM: ShinyROM 4.4.2
Kernel: franco.Kernel r395
Baseband: XXLJ1
Bootloader: PRIMED04
Also I don't know if this will affect things but for the record I'm running the latest Ubuntu and Debian.
So this post is pretty much a shot in the dark, since I think I know what I'm dealing with already; if anyone had this problem before in the past, or has it now and somehow managed to fixed it, please do tell. Or if anyone has any experiences RMA-ing your device with a condition like this I'd love to know.

Yep your EMMC is fried. Sorry man.. But you can go to warranty. They *should* accept it since it is a developers phone but they could make a lot of hassle about it being rooted..
Sent from my Galaxy Nexus using XDA Premium HD app

[Q] attempted kitkat revert, almost completely unresponsive

I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?

flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything

noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!

This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse

nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...

There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you

Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).

[Help] Stock S9 stuck in bootloop

SOLVED - Update below.
Hey guys,
I have an S9 (SM-G960F) which appears to have auto-updated during the night and as a result will now not boot. I am making an assumption it was an update of some sort as when I checked the time on it at 1am it was fine, when I woke around 8.30am the phone was off and when powering it on I ran into the issue. To summarise, I power the device on, get the Samsung loading screen, then the black swipe pattern screen to decrypt the phone, followed by the padlock unlocking loading screen, then the phone reboots. Sometimes however, the device gets past the padlock loading screen and says it is optimising apps, which is then followed by a reboot, briefly says it is installing system update before landing me at the Android Recovery screen.
What I've tried:
- Soft reset
- Booting in safe mode (same result as booting normally)
- Clearing cache partition
- Clearing app data
- Lacking storage booting (the device was quite low on storage last time I checked)
Some other (maybe) useful info:
I haven't updated the phone for months, could be why it did an auto update.
I'm on EE in the UK but IIRC the phone is not locked to EE.
Android Recovery has the following info when I load into it
Code:
samsung/starltexx/starlte
9/PPR1.180610.011/G960FXXU2CSB9
(options to try again, erase app data, power off, view rescue log)
#Reboot Recovery Cause is [system_server:12259 RecoverySystemRescueParty]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
Viewing the rescue log presents me with a stacktrace , the top of which is
Code:
*** FATAL EXCEPTION IN SYSTEM PROCESS: main
java.lang.RuntimeException: Failed to create service com.android.server.job.JobSchedulerService: service constructor threw an exception
(followed by the rest of the stacktrace I can get a picture of if necessary)
My goal here is to recover the photos on the internal storage as they don't appear to be backed up to Google photos, nor Samsung's alternative - which is particularly painful cause I'm the one usually preaching backups.
Is there anyway to recover the OS to retrieve data, or pull the data off the device without wiping it? I'm open to any suggestions on how to do this, the main goal here is saving my photos, hence why I have avoided a factory reset from the Android Recovery menu.
Hope I've been clear enough, but let me know if I need to clarify anything. I would greatly appreciate any suggestions!
Thanks,
Matt

Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt

Which version of Odin did you use?

majormatt said:
Hey guys,
After spending all day tearing my hair out with this I managed to fix it, so I guess this thread can be closed. For anyone who gets into a similar situation...
I attempted to solve this by flashing the current firmware using Odin and booting into "download mode", found a copy on sammobile.com. This didn't work, leaving me in the same situation, and as I felt I was running out of options I tried using the latest firmware for my device. I found a copy using a tool I found on these forums - Frija. Fired up Odin and download mode again, selected the AP/BL/CP/HOME_CSC (I understand using HOME_CSC is important so as not to cause a factory reset) and this worked! This left all of my files intact and as a bonus I'm also up-to-date with Android too. I'm backing up my photos as we speak as I would hate to be in this situation again!
Hope that can help someone in the future.
Cheers,
Matt
Click to expand...
Click to collapse
I would really appreciate it if you post a YouTube tutorial on how to fix this. Because we are facing the same problem right now but I have no idea what solution you prescribed. Thank you and God bless.