Develop Bugs

[Q] Help?

Hello All,
I've been browsing and searching pretty much all day, so I'm now going to ask for help.
Symptoms:
My screen is black. No white bars. Nada.
I know the phone turns on because the charging light goes off and the phone vibrates once when I press the down volume and power to go into recovery.
Preceding events:
I had just finished making a phone call, and the phone rebooted. I (was) running OMGB v6. When it came back, it started into a boot loop. It would run through the splash animation and then restart.
So, I decided to clear everything out and re-flash. Pulled my card out, wiped everything. Backed up my card, cleared it out, formatted it, and put the rom image in the root directory. When I tried to flash, I received the following error:
Cant mount /dev/block/mmcb1k0p1 (Invalid Argument)
Mounting /dev/block/mmcblk0p1 on /data failed: Invalid argument
I pushed parted (and a few other files) in adb and checked out what was going on. It looked like my phone's internal memory had somehow become screwed. So, I followed the directions outlined here:
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage (Sorry, can't post links yet. I'm not that cool. .smirk.)
When I got to the step of re-flashing PN31IMG.zip, Everything seemed to go through fine, then it rebooted and Voila! The screen is dead.
I think it may be because I have the slcd version, but I have no way of knowing for sure.
Any input or suggestions would be both welcome and helpful.

EDIT: Can you even get into hboot?
And you formatted your SD card as FAT32 right?
Probably a SLCD screen and the PB31IMG was for 2.1/AMOLED.
Try this guide. http://forum.xda-developers.com/showthread.php?t=786436
Flash the PB32IMG.zip in part 2. It's the stock 2.2 with support for the SLCD model. Thats just my 2 cents.

Input: In addition to searching and browsing, you should post your thread in the right section.
and yes as said above it was probably the incorrect screen version.

EDIT: I am doing just as you advised. Will post after trying. Thanks!
I am fairly certain that I can get into hboot, as this is what happens:
Press and hold down volume and Power
Wait 5 seconds, release power/volume down
Charging light goes off
Camera shutter clicks
I wait a good 15 seconds, just in case it's scanning my sdcard
Then, I presume it is in hboot and press the volume down key to move the selection to recovery, then press power to select, so that I can *hopefully* adb to fix it
It vibrates, as though going into recovery, But I can't see anything on the screen from start to finish, so I'm not sure.
And I have to be screwing it up somewhere, because no device is detected in adb

kaiserII101 said:
Input: In addition to searching and browsing, you should post your thread in the right section.
and yes as said above it was probably the incorrect screen version.
Click to expand...
Click to collapse
Thank you, kind sir.
As I am obviously ill-educated as to the correct place to post, would you mind pointing me in the right direction; or, as you agree with my assessment, offering a solution?

Update:
So, I finally got the timing right and booted the phone enough to get to adb.
I pushed parted and associated files to the phone and re-partitioned the internal memory (Swap, EXT2, FAT32), then disconnected from the computer.
I pulled the battery for 30 Minutes. Unnecessary? Probably. But I'm saying what I did just in case someone else has this issue.
While the battery was pulled, I downloaded:
ttp://dougpiston.com/files/RUU/build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
I formatted a 4gb card FAT32, and loaded said zip on the card's root directory. Then I turned the phone on and held the down volume to enter hboot.
I waited 5 minutes. Then I pressed the up volume key to confirm installation aaaaaaannnnddd......
I waited. 15 minutes this time. Then I pressed volume up to confirm phone reboot. 90 seconds later my screen came on, and booted into VZW stock!
Oh, and kaiserII101 - I would like to extend my personal thanks to you for pointing out that this was in the wrong thread.... ..... and then not responding. Where I come from, that's called asshattery. Not appreciated. Next time you feel obliged to make a snarky comment instead of actually being helpful, do us all a favor: Don't.

dismal moron said:
Update:
So, I finally got the timing right and booted the phone enough to get to adb.
I pushed parted and associated files to the phone and re-partitioned the internal memory (Swap, EXT2, FAT32), then disconnected from the computer.
I pulled the battery for 30 Minutes. Unnecessary? Probably. But I'm saying what I did just in case someone else has this issue.
While the battery was pulled, I downloaded:
ttp://dougpiston.com/files/RUU/build-3.26.605.1-release-152016-baseband-2.15.00.07.28-hboot-0.92.0000_PB31IMG.zip
I formatted a 4gb card FAT32, and loaded said zip on the card's root directory. Then I turned the phone on and held the down volume to enter hboot.
I waited 5 minutes. Then I pressed the up volume key to confirm installation aaaaaaannnnddd......
I waited. 15 minutes this time. Then I pressed volume up to confirm phone reboot. 90 seconds later my screen came on, and booted into VZW stock!
Oh, and kaiserII101 - I would like to extend my personal thanks to you for pointing out that this was in the wrong thread.... ..... and then not responding. Where I come from, that's called asshattery. Not appreciated. Next time you feel obliged to make a snarky comment instead of actually being helpful, do us all a favor: Don't.
Click to expand...
Click to collapse
Most cool - glad that worked, and thanks for posting the means to correct it so others may benefit from your experience!
Had a similar thing happen as well a while back ~ since then, I've made weekly copies of my SD card onto my PC - overkill perhaps, but then there's always a full backup of my goodies.
Happy modding!

I'm glad you got it working and I'm even more glad that I don't have the SLCD version of the Dinc. They just have so many issues...
Have fun!

huawei mytouch root

I've been working on this for the past week. Every exploit I've tried just hangs after a while. I've gotten much further manually. I've got unbuntu and been working using various manual methods. The thing I've noticed is that there is no system folder in root. There is a system partition in which app and bin folders exist. Later today I'm going to have time to try some more. If it weren't for these silly rules id reply to somebody elses post, but I guess reading in forums for 3 years as a registered user doesn't count. Never a need to post as I've always found something using a search. And now I've got a phones that's been out for a week and there's no info out on it so I guess I get to develop myself. Not a hard thing...just time consuming and I've got better things to do, but these pink apps gotta go and I need wired or wireless tehter again. Hopefully I have succcess later today and can post how I accomplished it.

I'll be waiting anxiously. please post updates in this thread with your progress!

Any progress on this? I have been attempting but no luck.

update on progress
jb0ne said:
I'll be waiting anxiously. please post updates in this thread with your progress!
Click to expand...
Click to collapse
ok so here's what i've learned so far from trying every method that i can find...
when you boot the phone into the pink screen (volume up and volume down plus power) there is a partition containing 1 folder with 5 files. That folder is called image and the file inside are amss.mbn, boot.img, cust.img, emmcboot.mbn, and recovery.img
The Ascend G300 is a similar phone to the G312 and there is a filed called superrecovery which changes the recovery to set ADB with root priveliges and installs SU in system. If we use the recovery from that batch file made by PauloBrien and push it to the device while in pink screen mode and then reboot into recovery the phone won't power on. You can return to the pink screen and change back to the original recovery, but you can not boot the device into recovery nor regularly. Now this gave me an idea as i'm typing. what if i change it and issue the command in ADB as ADB works during the pink screen. I'm going to try that now.
But this can't be done when in bootloader, only in pinkscreen which makes me think it's fastboot USB mode, but fastboot commands dont work uless you are in the bootloader with the huawei logo which you can only get into by issuing the reboot-bootloader command through adb. once you enter bootloader mode via ADB reboot command then you are able to issue some fastboot commands.
ok so that didn't work...basically when the files in the imge folder are changed the device won't boot into anything but the pink screen mode.
the original recovery file size is 6340KB and the one from PauloBrien is smaller at 5074KB. I'm wondering if file size has something to do with why it won't boot, however, i'm not familiar with what's inside of these files. So...as i reasearch how to build our own clockworkmod recovery i'm wondering if there's a way to change the ADB command inside from not root to root. if it's a on off selecton i'm not sure how i'd affect file size. this is where we get into the realm of knowledge that i don't possess.
so if anybody can offer up some knowledge from where i stand now... please do so.
on a side note, when running exploits, (gingerbreak, zergrush, doomsomething, psneuter, etc)...they all hang.
in linux when trying to drop a file into /system/bin the terminal read out says something about failing to cycle power, not certain what this means.
as i learn a bit more, i'll go ahead and add more...

I am hopeful to hear back from you with a successful root method for this device. I myself just purchased this phone for myself and would really love to see more development on it. Seems like a solid phone with a low entry price. Look forward to seeing what you come up with.

I'm also waiting anxiously for someone to figure this out. I just got this phone and while I really like it, there is just so much packed on this thing that I want to get rid of before I can really enjoy the phone.

I'll be watching this thread as well hopefully OP or someone else will figure out the trick to rooting this phone, like others I have used the usual methods but no luck. I've counted no less than 13 programs I'd uninstall right off the bat.
For what its worth the phone seems to not be considered part of the Ascend models of phones although they are quite similar our model is called the Unite U8680 and the Unite Q U8730 (the slider version). I've sent a email to Huawei lets see if they respond at all.
It's pretty much useless but this is all I can find on the G312 on the Huawei website:
http://www.huaweidevice.com/worldwide/technicaIndex.do?method=gotoProductSupport&productId=4086&tb=0

I'll be watching this thread as well. According to a post on another forum regarding a different Huawei model, dialling *#*# 2846579 #*#* and making some changes in the log file settings suddenly made their phones rootable for some reason. However while the same # gets you into the service mode on this phone, the log file changes made no difference.
I wonder, though, there are quite a few other options in that service mode. Maybe something in there that could be useful.
Edit: There's one menu that looks interesting, the USB one. You can change it to all sorts of modes including "Manufacture mode" whatever that is. Afraid to try it, don't want to brick my wife''s new phone

I've been playing with this menu as well and some of the USB modes do seem interesting. I was hoping this would let me find the product ID for the phone cause I found a link on the Huawei homepage to register to get an unlock code for the boot loader on this phone. If anyone is interested here is a link to the page and sadly the method they say to find the product ID doesn't work on our phone.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=toApplyUnlock

huawei says the product ID is an 8 digit number. I've been trying to dump the log files so i can scan them for some kind of 8 digit number. i've also tried all the different USB modes as well as a few other changes in the project menu that we're able to access. These haven't given me any success in changing the ownership of the folders needed to gain root access. i've not had any time to tear apart the recovery image to figure out what it's doing. but all in due time somebody will figure this out. still haven't been able to get fastboot to work properly either. am running through the usb modes on that now.

Yes please help i cannot figure out out either

builder.clockworkmod.com
so i've been working on building a recovery image for this devices using koush's site and have been able to build it, but the device won't boot into recovery yet. not sure how to fix this, gonna mess around and keep on trying. i can get it to boot back up and can get it to respond to adb commands when in the mode that just shows the android 4g logo. but i can't get into recovery. not through adb and not through using the power and volume buttons.
still working on it... any body else have anything yet?

No info on rooting this phone but Huawei just posted on their website the open source gingerbread kernel for the G312 U8680 here is a link to it:
http://www.huaweidevice.com/worldwi...=toDownloadFile&flay=software&softid=NDY3MzU=

It's been rooted!
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!

jb0ne said:
Yep, it's a simple one too. Happy to have my wife's phone rooted Removing bloat, however, is tricky -- it's hidden in an inaccessible partition and when you erase it, it restores it on next reboot.
http://forum.xda-developers.com/showthread.php?p=31237225#post31237225
http://www.droidrzr.com/index.php/topic/4276-how-to-root-huawei-mytouch-4g/
Big thanks to mattlgroff for cracking this nut!
Click to expand...
Click to collapse
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.

jamonthis said:
When you install an update to one of these apps lets use the, yahoo mail on for example, it will show in the /system/app or /data/app. The problem is the apk before the update is in /cust/t-mobile/us/app which is read only and unable to be mounted as R/W and that is why Titanium backup is unable to uninstall it.
I have tried moving it and deleting it manually with no luck. I have not tried through ADB yet but may give that a try next.
Click to expand...
Click to collapse
If you figure it out and find anything out I would love to know about it. Where should I watch for an update in case someone does get that sorted out?

Recovery mode
There is an accessible recovery mode, at least on my querty version of the phone. You have to completely pull the battery first. Put the battery back in, hold Volume up, and then hit power. I held the power button for a couple seconds, and volume up for maybe 6-8 seconds, then started hitting volume up repeatedly. The key is to pull the battery each time you try, I think. It looks like powering off from the phone's power menu just puts it in a suspend sort of mode. (Compare boot times when rebooting, and when pulling battery)
Apparently the bootloader is locked, so not sure how useful it is yet.

For anyone with a T-Mobile MyTouch Q (Huawei U8730), I created a wiki page for it, and we should post in the New Device Forum Requests thread so we have a specific place to post info.
I just purchased a U8730 today and will definitely be figuring out how to root it at some point.

For anyone that cares here's a link in case you haven't registered at the other site.
http://j.gs/1U5q

I'm hoping we can get some development going for this phone. I just picked one up for my daughter a month ago and it's giving her memory filled messages already. It'd be great if we can get it permanently rooted and remove bloat to start... then possibly move onto Cyanogen... considering she had the horrible Comet (also by Huawei) previously and it had development for CM7. I may be taking a leap from my contract soon, but can't go to Straight Talk with her phone unless it's unlocked

[Q] Tried to update, now unuseable

So I have upgraded my i927 captivate glide using the ROM from , but I only Androidupdate com called I927UCLH2_I927ATTLH2_I927UCLH2_Home tar md5 but I get a black screen with a slide down menu saying the date ‘Ongoing’ and an option to change the way that the device connects to another computer.
The update stated pass, it booted and proceeded to tell me that it was updating apps or something like that, then a black screen with the pull down menu from the top of the screen near the usb symbol came up but nothing else. I got a message a few hours later stating that the update application or something like that was not responding and an option to wait or quit. I chose wait, but nothing came of it eventually.
I then proceeded to try reflashing the process with no success even after factory reset and rebooting.
I then tried the pre-release ICS update as per XDA developers and other websites. Same thing
I tried a few other ODIN programs and ROMs but no success. Same issues including the hang up on the Samsung logo. I tried rooting it once and for some reason it started up into what looked like the same pull down menu, but it was requesting that I needed an to input a lock code for the network. I assume that is because my sim card was in it by now, but maybe not. I got so frustrated that I tried the bootloader and update bootloader options using the official ICS update ROM for some stupid reason but nothing. The thing is that at least it booted into the pull down menu that i got with a black screen again.
I then flashed with an updated ICS, CWM6 but cannot do the:
Third: Reboot into CWM6 (Volume- and power) install from sdcard (superuser)
Link to superuser: Superuser-3.2-RC2-arm-signed zip
Forth: Repeat third step above but install keyboard fix.
Link to keyboard fix: CWM_keyboard_backlight_fix zip
since I do not have an SD card that is working. I did get the SD Card in the device but I have always had problems with the format of it and I cannot put the zips onto the card due to the computer Win7 not recognizing it. I tried reformatting the device is HPUSB format program and windows. I inserted the card into the device to hopefully have it recognized on windows, and i gave me an option to format the SD card. So I proceeded and success. I was able to put the Zips onto the card. However, I returned to the CWM6 screen by pressing the VOL- and power keys but the files were no where to be found on the SD Card.
I moved on after a few other tries at it, so I tried to go backwards to the Gingerbread ROM. No success, same hanging issue at the Samsung logo.
I then tried to reflash with the devices original ROM as provided by DroidAngel on androidupdate com. Both without success.
I wanted to try the process involved on the 'stuck on boot screen' thread, but I cannot access the zip files on the sdcard in order to be able to do that.
I also bought my phone unlocked from the US (ATT version) and had it sent to me in Canada unlocked so I cannot just return it to the seller to get a new one, so my new phone is pretty useless.
I have spent two days reading through and trying different fixes and updated ROMs on multiple sites but I just cannot figure out what the heck to do now. I know that this site is not to spoon feed people and I am a noob to all of this but I am out of ideas and cannot find anything else to help out.
Where do I go from here. Is there a possibility of reformatting EVERYTHING on the device including all partitions etc etc.? I mean the hardware is fine, it is just a software issue. I do this to my laptop whenever I get into a bind.

Have you tried booting into CWM and restoring factory?
sent from my captivate glide running ICS (NardROM 0.3 Rooted)

Just a note, the SD card you're seeing in CWMR isn't actually your physical SD card, its the internal phone memory. I don't think we have a version of CWMR that reads the real external SD unless modified. So anything you put on it won't show up there. The folder structure will look like ... /sdcard/external_sd/ where /sdcard/ is where you want to put your files for CMWR to see, /external_sd/ is your physical card you can take in/out.

I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.

EaglesIII said:
I have tried to reflash with CWM6 using ODIN v3. I didn't realize that the SD card that came up was actually a part of the internal memory. Thanks to you both for the help.
Any other suggestions since no matter what I do now the phone simply stops at the Samsung logo and wont turn off? I press the power button for the required time to shut it down but it automatically restarts by itself to again sit at the Samsung logo.
Click to expand...
Click to collapse
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?

Evil Alex said:
A few questions about your situation right now:
Can you get into Download mode? (Turn off the device, in your case remove the battery. Press power en volume UP)
Can you get into CWM? (Turn off the device, in your case remove the battery. Press power en volume DOWN)
Does it keep asking you for the Network Key? Are you stuck at that particular point...?
Click to expand...
Click to collapse
Okay, so right now I can still get into the download mode to flash, the CWM6 to factory reset and reboot which I have tried already as stated, and I have not been asked for the network key again since the one time quite a long time ago. The network key is only asked when I load one of the other custom ROMS though, but I have not tried any of those in a while.
I am stuck at the black screen with white Samsung logo.

In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!

Got it running on Bio360 but 'Not Registered on Network' now
Evil Alex said:
In CWM6, do you see "mounts and storage" (Second to last option)
If so, connect your phone with the USB cable and select "mounts and storage".
In there and select "mount USB storage" (Again, second to last option, you'll have to scroll to get to it)
Now your PC should see the USB storage which is in fact what is marked as internal SD. So the sdcard CWM can actually see and install things from.
Now you can copy a custom ROM to it, and install it through CWM. Or install anything that is in CWM format.
You may get the Network Key Request as before. I do not know if it can be bypassed by starting it without the SIM. If so, you could then try to unlock your device using one of the methods on the forum.
Alternatively, and highly recommended by yours truly, is to buy the unlock code.
It is somewhat common for these devices to re-lock, so having the code handy is very convenient. I used americanunlocker to get mine, and I put the code on the inside of the back-cover should I find myself re-locked in the middle of nowhere. The code works, and isn't that expensive. In fact, it's a steal if you look at your own time invested in all this in terms of hourly wage! Of course, you'll need the IMEI code. You can find that by removing the back-cover and the battery.
Good luck!
Click to expand...
Click to collapse
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.

EaglesIII said:
Thank you so much for the feedback, I actually had not thought about the unlock code idea, and since you put it into such perfect terms considering the time and effort that has to go into something like that, it is a good idea for sure to get one. The idea of keeping it on the inside of the back cover is another awesome idea. Kudos to you and thanks!
As for the rest of what you had stated about the mounting and what not; I actually mounted and successfully reflashed and installed all of the required files for the new ICS stock upgrade. The good news was that I got past the Samsung screen again and it said that it was updating all of the applications or whatever again, but then it just gave me the pull down menu again with very limited functionability.
I then used your suggestion to try out another ROM. I tried the Bio360 and followed all directions on the 'phone stuck on boot screen thread'. It worked! I finally have a functional phone again and will be able to get calls from my boss. Thanks!
Now that I know I have one option, I can explore any other options. I still cannot figure out how it is that I will be able to get the ICS upgrade but maybe I will try Kies.
However, I just found that I don't have network access anymore despite that I have a strong cell signal, so I presume that I will have to enter the unlock code somewhere. Where can I put that into? It didn't pop up to tell me anything.
Click to expand...
Click to collapse
You're very welcome! Glad to hear the phone is usable again. In order to get data back you will have to set your APN manually. Stock ROMs come with the APN settings for all providers it is expected to be sold with. But custom ROMs usually come without those settings. You can find the APN settings for your provider online, just do a search. There is even an app for it, but the name eludes me at the moment. You'll need wifi to get the app, though! Once the settings are in place (You put them in under wireless & Networks), you'll have data again.
As for the limited functionality, I had the same thing, at first. The upgrade was broken for me, I guess some settings/apps were causing problems. So, after flashing the upgrade, I did a factory reset in CWM. I also wiped the cache, and the Dalvik cache, for good measure(Under advanced in CWM). It rebooted, said it was upgrading and installing, and I let it sit for a few minutes. Then I was greeted by an initial setup screen, and the phone has been on a working ICS ever since! I did lose all my settings and such, but I had a back-up of those with Titanium Backup, and got those back that way.
Hope this will help as well.

Help with Note 4 please

I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT

RootieTootie said:
I may have a bricked phone on my hands, my fault I guess.
Although, I feel TWRP should share at least some of the blame.
I'm hoping someone can help to get me going again.
Last Xmas I got a refurbished Note 4 from Ebay and followed directions
here to root it. This all went well, I put TWRP 3.0.2 and Jasmine on it,
and it has worked just fine since then.
A couple days ago I realized I hadn't made a Nandroid backup of my phone
lately so I went into TWRP and did so. This went just fine and I stored
the backup on the external SD card.
A few hours later I bought a cheap home controller from Ebay. The controller
brand name is "Vera" and despite all of the negative comments on Google Play
I went ahead and installed the app. For the next day or two my phone began to
hang, stall, hesitate, whatever... and I remembered installing that app from
Google play so I went into the app manager and selected the uninstall option.
This caused the phone to hang indefinitely, I had to cycle the power button to
regain control. I then went back to Google Play and downloaded an uninstaller
program, told it to uninstall the vera app. It tried for a long time but
eventually gave up. "Uninstall failed" was all it would say.
So to stop this Vera app from hanging my phone I ran a freeze program ("Freeze"
is the actual name of the program) and had the vera app frozen. This worked, my
phone began to respond normally again. But I didn't like having this bad software
in my phone and that is when I remembered the recent TWRP backup.
I decided to do a complete restore with TWRP. TWRP did a restore of boot - (success),
recovery - (success), system - (success), data - "ERROR extractTarFork() process ended
with ERROR=255". Thanks TWRP, that really tells me a lot...
I repeated the restore effort a total of three times and same results. Google
wasn't much help, one suggestion was to unmount the data partition and try again.
Same results. Same error. Another suggestion was “stop and learn how to fix it”, well
sure, but I need a solution right now, I don’t have time right now for the learning part.
This is probably my first *big* mistake, I exited TWRP to see If I could boot
the OS and maybe fix it from there, (factory restore or something...). As you might
have guessed, it wouldn't boot the system with an incomplete data partition. I
suspected it too but I was desperate to try something. It would have been nice if TWRP
had warned me not to exit, instead of just saying "error 255..." because now it wont
boot back into recovery, just hangs. Odin mode appears to be working but I suspect it isn't.
It looks like it enters odin mode just fine, but odin can't see it.
So here is where it stands at the moment:
SYSTEM - Wont boot. Shows the Samsung logo, shows "custom", hangs at this point.
RECOVERY- Wont enter recovery mode. Small text in upper left says it is entering recovery
mode then it hangs.
ODIN/DOWNLOAD - Appears to enter this mode, usual screen appears, will not communicate
with Odin, will not communicate with adb.
One other note, the external sd card has a copy of the twrp log file written to it, as well
as the nandroid backup. But plugging the sd card into an adapter and then into a pc... It
says it can’t read it, and would I like to format it(?).
And of course there is valuable information on the phone.
I've run out of ideas, I'm asking anyone who is still reading this lengthy message(apologies)
for any other options, suggestions, any hope at all, instead of just throwing it in the trash.
Thanks for reading. I hope the dialog was understandable.
RT
UPDATE:
Progress. I have odin talking with the phone now, was able to re-flash TWRP and boot into it.
Still getting error 255. I am under the impression that this means I am out of space???
I pulled the recovery logs with adb, here is the relevant lines:
==> extracting: //data/app/radiotime.player-1/lib/arm/libtunein.uap.so (file size 5499572 bytes)
I:Unable to extract tar archive '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001'
Error during restore process.
I:Error extracting '/external_sd/TWRP/BACKUPS/657e54fc/2017-04-08--07-58-24_JasmineROM_v7.0-MMB29M.N910VVRU2CPF3/data.ext4.win001' in thread ID 0
I:Error extracting split archive.
Error during restore process.
extractTarFork() process ended with ERROR: 255
I:Set page: 'action_complete'
Iperation_end - status=1
I still don't understand "error 255" well enough to proceed. Google is not a wealth of information when it comes to this subject. Any suggestions on how to proceed are greatly appreciated.
thanks!
RT
LAST UPDATE:
I want to thank everyone here for all the help. Or the lack there of.
Since I had Odin and TWRP both working, I reconstructed the phone from scratch.
Re-rooted and re-installed Jasmine. So I am back up and running now, I just need
to get all the apps re-installed and configured.
But I must say that I am really disappointed with the lack of support from this forum.
It used to be that people were falling all over each other to help others out.
But 3 days and 49 views and not one of you had anything to say.
I guess that's what happens to all forums sooner or later, the newbies here don't know what
to say and are just looking for answers to their own issues, and the regulars become jaded
over time and can't be bothered anymore.
I used to think this forum was awesome, but now its just another forum like all the rest.
I will look to other websites for any future learning.
To the Admin: (If you can be bothered for a moment)You can close this thread, I consider
the issue resolved, and you can close my account too, I won't be back.
Good luck to you guys.
RT
Click to expand...
Click to collapse
sorry we missed your call gratz on the working phone . you know what they say "give a man a fish he ****s up his phone .....

[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.