Related
I've been rooted with unrevoked3 (and I have verified that I have S-Off) for a few months now and I've gotten at least a decent feel for what you can do with a rooted evo. I've gotten used to a few adb terminal commands also. The next big thing that I'm trying to do is install a cyanogenmod 6 rom on it (and eventually update it to 7 after it's no longer a nightly). I've already done a nandroid backup, titanium backup, and I have a copy of my RSA keys. I've read through the installation instructions for cyanogenmod 6 (http://wiki.cyanogenmod.com/index.php?title=HTC_Evo_4G:_Full_Update_Guide) and it mentioned flashing the radio. I'm not worried about doing that part, but I want to know if the changes that I make to it will be reversible or not if I decide that I don't like cyanogenmod. Finally, if there's anything that I'm missing, or if there's an easier way to do this other than the link I posted, any advice/tips would be great.
spalding1028 said:
I've been rooted with unrevoked3 (and I have verified that I have S-Off) for a few months now and I've gotten at least a decent feel for what you can do with a rooted evo. I've gotten used to a few adb terminal commands also. The next big thing that I'm trying to do is install a cyanogenmod 6 rom on it (and eventually update it to 7 after it's no longer a nightly). I've already done a nandroid backup, titanium backup, and I have a copy of my RSA keys. I've read through the installation instructions for cyanogenmod 6 (http://wiki.cyanogenmod.com/index.php?title=HTC_Evo_4G:_Full_Update_Guide) and it mentioned flashing the radio. I'm not worried about doing that part, but I want to know if the changes that I make to it will be reversible or not if I decide that I don't like cyanogenmod. Finally, if there's anything that I'm missing, or if there's an easier way to do this other than the link I posted, any advice/tips would be great.
Click to expand...
Click to collapse
Undoing it would be as simple as restoring that nandroud backup you made. It sounds like you're ready. Have fun!
Sent from my PC36100 using XDA App
+1 sounds like you've done your homework.....you can go right back to your nandroid in the very small chance you don't like CM.... and when you restore your nandroid it will be as if you never changed anything in the first place...
The radio is a two step process. It will flash in recovery and then reboot and finish writing the radio. You have to let the second part complete or you will brick your phone.
Quick question based on the OP's question: Do we have to update radios when we flash a new rom? I was also looking to install CM7 as my first flashed rom today. I already have the most current radios, as my phone is only a couple weeks old, and has all the sprint updates. I am rooted just running the stock rom for right now, so do I have to flash radios even though they are the same version that I have now?
You don't HAVE to update the radios to the latest. I haven't updated either since I received my new Evo. "If it ain't broke ...." Could just give the ROM a go and see what happens. If you feel like it's necessary you can give it a shot. You can always go back if a new one doesn't appear to be working as well. It's not required, and it's not "un doable."
Sent from my PC36100 using XDA App
Yea if you get slow internet or bad service a fresh radio flash can't hurt. But as it was said earlier, let the radios flash! I screwed up and pulled my battery because I thought it wasn't working but all I did was end up breaking my rsa keys.
Swyped from my Evo on steroids.
TheSilverStig said:
Yea if you get slow internet or bad service a fresh radio flash can't hurt. But as it was said earlier, let the radios flash! I screwed up and pulled my battery because I thought it wasn't working but all I did was end up breaking my rsa keys.
Swyped from my Evo on steroids.
Click to expand...
Click to collapse
Yea I believe only 3.70 requires you to have the new radios other than that just enjoy life nandroid and flash away. Like said earlier "if it aint broke" and since mine are working fine I have not updated my radios and the fact that I run Gingerbread and not one of these new 3.70 roms makes my decision easy.
Okay, I've got cyanogenmod installed, I'm doing a nandroid backup right now, and my big questions now, if I want to switch between cyanogen and what I had before installing it, can I just nandroid between the two? and can I use Titatium to reinstall all of the apps I had before installing cyanogen without problem?
spalding1028 said:
Okay, I've got cyanogenmod installed, I'm doing a nandroid backup right now, and my big questions now, if I want to switch between cyanogen and what I had before installing it, can I just nandroid between the two? and can I use Titatium to reinstall all of the apps I had before installing cyanogen without problem?
Click to expand...
Click to collapse
If you made a nandroid before switching, the nandroid will save EVERYTHING, including your apps. So if you want to switch back and forth, make a new Nandroid for CM (make sure you know which one is which), then you can boot into recovery and restore the old one, and restore the CM one whenever you want. No need to use titanium once you have made a nandroid.
Awesome. I said what the heck and experimented and found out I could do that yesterday. The one last thing that I'm trying to do now is to backup all of my sms to the sd card so I can restore them in cm. I'm gonna search around for an app for now until someone points me in the right direction.
Sent from my rooted PC36100 using XDA App.
spalding1028 said:
Awesome. I said what the heck and experimented and found out I could do that yesterday. The one last thing that I'm trying to do now is to backup all of my sms to the sd card so I can restore them in cm. I'm gonna search around for an app for now until someone points me in the right direction.
Sent from my rooted PC36100 using XDA App.
Click to expand...
Click to collapse
You can use mybackup pro or titanium backup
Sorry, wrong thread.
I've had Titanium Backup (Pro) for quite a while now, and up until now it's worked like a charm.
However, today it seems it's decided not to restore backups anymore.
Every time I try to restore an app it just notifies me that "Data restore failed for APPNAME"
I've tried multiple backups, and even tried making new ones and restoring them, but nothing works.
Titanium did update recently, so maybe that broke it, but I was just wondering if anyone else was having similar issues.
same here
I'm having the same issue on my thunderbolt after updating to BAMF 1.7 and the latest titanium...
I started to notice the same thing happening to my phone last night, I don't remember updating though, but I may be wrong.
Ditto here on N1 coming from CM7 to a Sense ROM. I haven't had issues until today.
Will look for the previous version to see if it fixes it.
Well mine will restore any apps that are backed up, but the data fails to restore. I'm on SFR 1.1.1 on my Epic
Uninstall the current version and install 3.8.4 until they release an update.
Google, 2nd link, halfway down the page
Sorry, I didn't provide the direct link so as not to break any rules
Dman10 said:
Well mine will restore any apps that are backed up, but the data fails to restore. I'm on SFR 1.1.1 on my Epic
Click to expand...
Click to collapse
That's actually the problem I've been having, I just worded it wrong.
I guess it must've been the Titanium update if it's happening to people across different phones/ROMs.
I'm running Simply AOSP 3.1.1.
Guess we all just have to wait for it to get updated again, hopefully fixing the issue.
I just found an older version (3.8.2) on the developers website that works: http://matrixrewriter.com/android/files/TitaniumBackup.apk
Wow, today was my first time using Titanium Backup, and I spent hours going crazy trying to get it to restore system and app data. Using the older version mentioned above worked perfectly. Thanks!
oops I thought I messed up with RFS and ext4 so now I get no more candies feels good to have few others with me not that I wish for problem to stay
I believe they just released an update that fixes this issue.
Sent from my SPH-D700 using XDA App
Yes, this is resolved in 3.8.5.2. Thanks to everyone!
i would love to create a nandroid backup for my galaxy s 3 (sgh-t999)... but i keep getting these error messages when i am doing the backup through cwm
"unable to find volume."
"Error finding an appropriate backup handler."
does anybody know how to fix this? i know that this is not something that will impede my daily use of the phone but since i flash roms, it is a great idea to have a backup just in case.
does anybody have any ideas on how to fix this... or has anybody dealt with this before?
Having the same issue on my AT&T
have you tried other versions (even older) of clockwork? There were issues like this for Sprint, going back to 5.8.4.5, eve though v 5.8.4.8 was available, did the fix. try that
hes right, went to rom manager and looked at available recoveries at the bottom and picked the oldest one available which was .5 and now i can make backups, and have access to the external sd, yay
Good deal... Click thanks....
Sent from my SPH-L710 using xda premium
Naddict said:
have you tried other versions (even older) of clockwork? There were issues like this for Sprint, going back to 5.8.4.5, eve though v 5.8.4.8 was available, did the fix. try that
Click to expand...
Click to collapse
thanks for the suggestion... i tried that. there were two older versions. the one that was .5 wasnt even able to mount the sd card. the .6 version had the same issue as the latest version.
also... might mean nothing... but i noticed that when it tries to do a backup, i dont see cwm scrolling through all of the files like it is backing up like it did with all my other phones. it says backing up data, but it doesnt like go through file by file. is that normal?
SOLVED!!!
found a post where it solved my problem... hope it works for everybody else. just deleting the ".android_secure" folder on my sd card solved everything.... its always the easiest solutions that seem to evade us. if it helps, you should thank the person who solved it
http://forum.xda-developers.com/showpost.php?p=21292655&postcount=42
First post, so forgive me if this isn't quite right. Been struggling with rooting/putting Cyanogenmod on my computer over the last few days/week or so. I took the OTA 4.3 update awhile back and hated it, but kinda bit the bullet and dealt with it. Rooted and put a custom recovery on it last week, everything went well enough, tried TWRP and CWM recovery and found I preferred CWM.
When I went earlier, after finally getting a nandroid backup done successfully (neither recovery could save the backup to my external SD card, but that's another issue altogether) I went to flash the CM 10.2 stable release from their website, and it threw an error 7 assert fail.
After failing to restore properly from the backup (somehow) and locking up at launch with com.google.apps has stopped working before I could even get my launcher to open, I finally just wiped the entire phone and booted from scratch to get it to "work", managed to not lose root in doing so as I've just checked and found out.
Point being, error 7 assert fail on a sprint s3 trying to flash cm10.2 from CWM recovery. I had the most up to date ROM manager and CWM (I believe). This all coming after I spent 4+ days failing to be able to have my recoveries make nandroid backups to my SD card (don't know if related).
At this point I've kind of relinquished to lose everything on my phone when I flash the new OS, so I kinda just wanna get CM on there already and remedy this issue altogether. Does anyone have any idea what could be causing this issue, and how to remedy it? Like I said, I'm running stock samsung ROM with the 4.3 update taken OTA.
If anyone has any insight I'd really appreciate it, I know it shouldn't be as difficult as it has been to deal with all this stuff but after lurking for over a week to try and find an answer I just have to ask myself.
Thanks.
MTSL_Mantra said:
First post, so forgive me if this isn't quite right. Been struggling with rooting/putting Cyanogenmod on my computer over the last few days/week or so. I took the OTA 4.3 update awhile back and hated it, but kinda bit the bullet and dealt with it. Rooted and put a custom recovery on it last week, everything went well enough, tried TWRP and CWM recovery and found I preferred CWM.
When I went earlier, after finally getting a nandroid backup done successfully (neither recovery could save the backup to my external SD card, but that's another issue altogether) I went to flash the CM 10.2 stable release from their website, and it threw an error 7 assert fail.
After failing to restore properly from the backup (somehow) and locking up at launch with com.google.apps has stopped working before I could even get my launcher to open, I finally just wiped the entire phone and booted from scratch to get it to "work", managed to not lose root in doing so as I've just checked and found out.
Point being, error 7 assert fail on a sprint s3 trying to flash cm10.2 from CWM recovery. I had the most up to date ROM manager and CWM (I believe). This all coming after I spent 4+ days failing to be able to have my recoveries make nandroid backups to my SD card (don't know if related).
At this point I've kind of relinquished to lose everything on my phone when I flash the new OS, so I kinda just wanna get CM on there already and remedy this issue altogether. Does anyone have any idea what could be causing this issue, and how to remedy it? Like I said, I'm running stock samsung ROM with the 4.3 update taken OTA.
If anyone has any insight I'd really appreciate it, I know it shouldn't be as difficult as it has been to deal with all this stuff but after lurking for over a week to try and find an answer I just have to ask myself.
Thanks.
Click to expand...
Click to collapse
Status 7 doesn't have anything to do with your choice of recovery, it is because your bootloader is not listed in the get prop of the older ROM releases. You need to modify the assert lines to match your current bootloader or delete them altogether for something like CM 10.2 or any other ROM based on AOSP 4.3.x; realistically, I would just recommend jumping straight to KitKat 4.4.x, the asserts will reflect your current bootloader. Also, I would very highly recommend switching to Philz Touch recovery, it is based on CWM, but it is really like CWM on steroids.
Mr. Struck said:
Status 7 doesn't have anything to do with your choice of recovery, it is because your bootloader is not listed in the get prop of the older ROM releases. You need to modify the assert lines to match your current bootloader or delete them altogether for something like CM 10.2 or any other ROM based on AOSP 4.3.x; realistically, I would just recommend jumping straight to KitKat 4.4.x, the asserts will reflect your current bootloader. Also, I would very highly recommend switching to Philz Touch recovery, it is based on CWM, but it is really like CWM on steroids.
Click to expand...
Click to collapse
I was going to just jump right into using one of the nightly CM11 builds but I saw a few places people were having some bugs (as is expected with a nightly) and wanted to try to stick with a stable release for right now.
So if I go into the updater-script and change/remove all of the get-prop commands it should work? There's no chance of that causing any other issues?
I had philz when I first rooted the thing, and someone suggested that I switch to twrp when I started having the not-being-able-to-make-a-nandroid-on-my-external-SD-card problem, but I didn't care for it and ended up getting the most current CWM recovery just to leave it. I don't have any complaints about it as is, except the frustration I have with the entire process so far of trying to get this thing situated.
MTSL_Mantra said:
I was going to just jump right into using one of the nightly CM11 builds but I saw a few places people were having some bugs (as is expected with a nightly) and wanted to try to stick with a stable release for right now.
So if I go into the updater-script and change/remove all of the get-prop commands it should work? There's no chance of that causing any other issues?
I had philz when I first rooted the thing, and someone suggested that I switch to twrp when I started having the not-being-able-to-make-a-nandroid-on-my-external-SD-card problem, but I didn't care for it and ended up getting the most current CWM recovery just to leave it. I don't have any complaints about it as is, except the frustration I have with the entire process so far of trying to get this thing situated.
Click to expand...
Click to collapse
Yes, you will be able to flash 4.3.x AOSP ROM's by modifying/deleting the assert (get prop) lines. The reason those lines exist in the first place is so that someone on TMobile doesn't flash a ROM meant for Sprint, when the phone is the same but available on multiple carriers. As long as you choose a d2spr ROM you are fine. I am personally loving CM11 and CyanFox 4.4.2, they have both been very stable and awesome for me, but I also don't use things like Bluetooth, and my area has no LTE yet, so I wouldn't even notice problems of those types in the first place. And again, I recommend (extremely highly!!) Philz Touch recovery, I have yet to see anyone complain about issues with Philz that I have seen complained about from CWM or TWRP.
Mr. Struck said:
Yes, you will be able to flash 4.3.x AOSP ROM's by modifying/deleting the assert (get prop) lines. The reason those lines exist in the first place is so that someone on TMobile doesn't flash a ROM meant for Sprint, when the phone is the same but available on multiple carriers. As long as you choose a d2spr ROM you are fine. I am personally loving CM11 and CyanFox 4.4.2, they have both been very stable and awesome for me, but I also don't use things like Bluetooth, and my area has no LTE yet, so I wouldn't even notice problems of those types in the first place. And again, I recommend (extremely highly!!) Philz Touch recovery, I have yet to see anyone complain about issues with Philz that I have seen complained about from CWM or TWRP.
Click to expand...
Click to collapse
I did what you suggested and removed the assert statements at the start of that script. This time it didn't throw the assert but still failed. It said "installing update" and then immediately threw "installation aborted" a second later without any other information..
MTSL_Mantra said:
I did what you suggested and removed the assert statements at the start of that script. This time it didn't throw the assert but still failed. It said "installing update" and then immediately threw "installation aborted" a second later without any other information..
Click to expand...
Click to collapse
Did you install Philz as well or are you still using CWM?
Mr. Struck said:
Did you install Philz as well or are you still using CWM?
Click to expand...
Click to collapse
No, it was still on CWM. I don't see how philz would change that behavior, philz wasn't able to perform backups on the external SD card either when CWM and TWRP couldn't, so I'm almost expecting them all the have the same issues, but I suppose I could be wrong.
Is there anything else worth trying? I feel like it shouldn't be this complicated, I have the right ROMs in the right places..
MTSL_Mantra said:
No, it was still on CWM. I don't see how philz would change that behavior, philz wasn't able to perform backups on the external SD card either when CWM and TWRP couldn't, so I'm almost expecting them all the have the same issues, but I suppose I could be wrong.
Is there anything else worth trying? I feel like it shouldn't be this complicated, I have the right ROMs in the right places..
Click to expand...
Click to collapse
Philz doesn't call your external SD by that name, it is called sdcard1. SDcard is the internal. All I can say is that, in my opinion, Philz is far superior, I would say give it another shot.
Sent from my SPH-L710 using Tapatalk
Mr. Struck said:
Philz doesn't call your external SD by that name, it is called sdcard1. SDcard is the internal.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
I misspoke, I meant sdcard1 (or ext_sdcard or however the other recoveries reference it). None of them have been able to do it with their respective names. But that's (possibly) another issue, I just mean that's why I'm not positive switching would help. I could definitely be wrong though, I can try it if nothing else next time I get to a computer with Odin send it over.
There is a flashable zip as well just FYI. As to your backup location issues, I don't know what to tell you, I've never experienced that problem.
Sent from my SPH-L710 using Tapatalk
---------- Post added at 08:43 PM ---------- Previous post was at 08:42 PM ----------
Also, I know some users have had better luck renaming one of the bootloader assert lines to match the MK3 boot loader instead of deleting all the lines.
Sent from my SPH-L710 using Tapatalk
Maybe I'll try philz out then but if not I'm stumped.. I know it sholdn't be this difficult to do this crap, I'm glad that I'm learning some of the pitfalls, but some of these pitfalls don't seem like things other people have been encountering so I don't know what the deal is.
So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU
Hi, you certainly have a challenge there. It sounds like you need to restore both the partitions and the stock OS.
If the phone is a 32 GB model, please see the whole thread at http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325
There is a PIT file linked at post 16, instructions for using it at post 22. Also a link for the latest stock TAR file.
Again, this would be for 32 GB model, but you want to flash first the PIT and then the TAR.
I think I may have done that already too but I'll look again once in home and see if maybe I did it in the wrong order. Thanks for the quick reply friend. ?
Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/
jbowman21 said:
Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/
Click to expand...
Click to collapse
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk
elesbb said:
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.
1619415 said:
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.
Click to expand...
Click to collapse
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.
elesbb said:
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.
Click to expand...
Click to collapse
Huh, if you remember, write a guide that way you can help people.
1619415 said:
Huh, if you remember, write a guide that way you can help people.
Click to expand...
Click to collapse
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.
elesbb said:
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.
Click to expand...
Click to collapse
Lol
1619415 said:
Lol
Click to expand...
Click to collapse
Yeah sadly I have no idea how the efs is populated. The second instance I get a new phone, dd is done on the efs partition and created into a .img file.
jbowman21 said:
So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU
Click to expand...
Click to collapse
Koop's firmware didn't work with my phone either. This version of it fixed mine for some reason. Try flashing it to yours
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Now i got same issue i accidently restored efs and ah man ive tried every thing it reboots after 2 or 3 mins no matter what rom back up i have and i have efs and radio with all my back ups ive restored it also no luck. Guess im going to the sprint store tomorrow even after i flashed stock 6.0.1 i can get to about half way through wifi setup before it reboots no matter what 2-3 minutes phone reboots unless in twrp
Still no luck becareful and dont try to restore efs i suppose in twrp. Your phone may never stop rebooting ive flashed 2 different 6.0.1 builds one was the revo other was from sammobil both @koop1955 has them PB6 6.0.1 odin doesnt fix this.
YOYOYO
Well wtf or omg it completely died left it for a day. Now its working so far it hasnt rebooted in 30 mins LOL but dude sucks going to a phone with kitkat after using marshmallow and one of the fastest phones made for awhile. I did pull the sim card out and try it in a old boost maybe that reset something idk its working though.My problems were Rebooting constantly after 2-3 mins no matter what rom i had even stock.
---------- Post added at 12:31 PM ---------- Previous post was at 12:11 PM ----------
Saafir said:
Backed up my EFS before ever even rooting. Stuck that bad boy in Dropbox for safety. *pats self on back*
Last one of these topics I seen, end result was JTAG.
Click to expand...
Click to collapse
BEcareful if u restore that efs. i backed up too but once in twrp. Now all i did was check restore efs by accident just tried restoring a renegade rom system,boot, and data. Tell you what i wont be rushing through crap and am fine with stock for awhile. Probably will still take the replacement when it comes its white the black one i got is too blue.
Saafir said:
I've got a raw partition backup as well as one through TWRP. If you check md5/sha hashes for data integrity, and only install software instances specific to your device, aside from manually monkeyin around
Hey needless to say im researching full partition backups did you use a app by wanam partitions back up and restore? Or just simple adb commands. Last used adb on a moto e 2nd with success on unlocking. Once i got a new harddrive haven't needed it.
Click to expand...
Click to collapse
Theres similar issues happening on sprint note 5s as well and has a couple threads currently speaking about this problem. Strange strange. It happened to me after updating to mm and then rooting.
Well i did try the note rom right before and when i did hit restore efs it after wiping system data boot from moar MM rom phone rebooted for days then after few resets and odin flashes i let it die then a day later it worked.
Correct but have always preferred the 925p roms.
Well i helped another with the rebooting issue on any rom.
He tried everything then but let it die after battery died plug it in and bingo his worked to
IF CONSTANT REBOOTING.
LET THE BATTERY COMPLETLY DRAIN.
AFTER FLASHING STOCK.