So I went ahead and just did it ran the ruu. So i been trying ways to unroot this as much as my not so experienced self is. Well first i tried to replace the rom.zip with an older one as if that was done it would be the easiest way. well replaced it but it didn't successfully flash once it got to the flash bootloader part. Then I booted to recovery and first thing it said was E:can't archive /cache/recovery/command. So I tried to apply update.zip it started to go through but got a signature failure. Anyways any help with this would be great
new pri 2.20_003
thatguythatdid said:
So I went ahead and just did it ran the ruu. So i been trying ways to unroot this as much as my not so experienced self is. Well first i tried to replace the rom.zip with an older one as if that was done it would be the easiest way. well replaced it but it didn't successfully flash once it got to the flash bootloader part. Then I booted to recovery and first thing it said was E:can't archive /cache/recovery/command. So I tried to apply update.zip it started to go through but got a signature failure. Anyways any help with this would be great
new pri 2.20_003
Click to expand...
Click to collapse
Throw it into the toilet and get a warranty replacement quick, before all the phones have 2.1.
Other then that, the only way to find root would be to have a good knowledge of linux, kernels, c, etc, and find known linux exploits and go down the list and try them.
robchaos said:
Throw it into the toilet and get a warranty replacement quick, before all the phones have 2.1.
Other then that, the only way to find root would be to have a good knowledge of linux, kernels, c, etc, and find known linux exploits and go down the list and try them.
Click to expand...
Click to collapse
I'm getting a new one today from craigslist so if I never post again then I'll be one of those when craigslist goes wrong stories on the news.
Also I never got the warranty from sprint I got the warranty from radioshack because they said that they cover everything but water damage. So right before I threw it off my roof I called radioshack to make sure they would cover it they said they only cover wear and tear and software.
I still would like to know how to make an sign an update zip though so I can flash it through recovery.
thatguythatdid said:
I'm getting a new one today from craigslist so if I never post again then I'll be one of those when craigslist goes wrong stories on the news.
Also I never got the warranty from sprint I got the warranty from radioshack because they said that they cover everything but water damage. So right before I threw it off my roof I called radioshack to make sure they would cover it they said they only cover wear and tear and software.
I still would like to know how to make an sign an update zip though so I can flash it through recovery.
Click to expand...
Click to collapse
First of all, do you have mac or windows?
Doesn't matter, The RUU removes root and the ability to flash a custom recovery, doesn't it?
HeroMeng said:
First of all, do you have mac or windows?
Click to expand...
Click to collapse
Sorry messing with the phone. I got a pc windows 7 64 blah blah. I did try to manual update but it wont let me because it says that main version is older.
robchaos said:
Doesn't matter, The RUU removes root and the ability to flash a custom recovery, doesn't it?
Click to expand...
Click to collapse
Yes and no. While in the new recovery it gives you the ability to flash an update zip from your sd but I get signature fails if I could fake the signature then I could flash a rooted rom and carry out from there putting a new recovery image and so fourth
thatguythatdid said:
Yes and no. While in the new recovery it gives you the ability to flash an update zip from your sd but I get signature fails if I could fake the signature then I could flash a rooted rom and carry out from there putting a new recovery image and so fourth
Click to expand...
Click to collapse
What happens if you try flashing any of the released roms out there, like fresh rom? It is signed using test keys. That would be crazy if the new recovery lets you flash any signed rom, but I predict it's locked down to HTC's keys which are privately encrypted keys. You can't fake them.
flipzmode said:
What happens if you try flashing any of the released roms out there, like fresh rom? It is signed using test keys. That would be crazy if the new recovery lets you flash any signed rom, but I predict it's locked down to HTC's keys which are privately encrypted keys. You can't fake them.
Click to expand...
Click to collapse
I've tried only tried a couple so far it takes a sec though cuz I gotta reboot to put anything on and I'll try the fresh 2.0d
Justg tried the original fresh 2.od and got signature verification failed
Going to pick up my new phone so if any body has anyideas on how to root this when I get back let me know. When we gonna get a leak that lets you sign with htcs keys
thatguythatdid said:
Going to pick up my new phone so if any body has anyideas on how to root this when I get back let me know. When we gonna get a leak that lets you sign with htcs keys
Click to expand...
Click to collapse
It should be 1.5, so just root it w/ http://forum.xda-developers.com/showthread.php?t=583291 and you'll be good to go.
thatguythatdid said:
Going to pick up my new phone so if any body has anyideas on how to root this when I get back let me know. When we gonna get a leak that lets you sign with htcs keys
Click to expand...
Click to collapse
i may be crazy.... but if we find a way to root this 2.1 before they release it couldn't they then patch that exploit? maybe this is why they "leaked" it so we could have a chance to find any holes or exploits in the software/bootloader/recovery?
regaw_leinad said:
It should be 1.5, so just root it w/ http://forum.xda-developers.com/showthread.php?t=583291 and you'll be good to go.
Click to expand...
Click to collapse
I meant the one with the 2.1 on it
thedudejdog said:
i may be crazy.... but if we find a way to root this 2.1 before they release it couldn't they then patch that exploit? maybe this is why they "leaked" it so we could have a chance to find any holes or exploits in the software/bootloader/recovery?
Click to expand...
Click to collapse
you may be right I thought of it but I don't know how clever they are considering how long it's taken them to put out the same rom we had back in march
thatguythatdid said:
I meant the one with the 2.1 on it
Click to expand...
Click to collapse
Oh, sorry my bad
regaw_leinad said:
Oh, sorry my bad
Click to expand...
Click to collapse
No problem . I'm glad that devs are looking at this maybe we can have a solution before the problem
sandboxlove said:
so the new recovery lets you flash updates? their just asking for us to better their software, jesus...
Click to expand...
Click to collapse
What like their gonna do it? I heard the ssamsung 2.1 update didn't even have live wallpapers
go to cyanogens wiki page. and find where he manually replaces the /radio partition.
if you have fastboot you can manually replace every partition this way. including /recovery.
just an idea.
Avalaunchmods said:
go to cyanogens wiki page. and find where he manually replaces the /radio partition.
if you have fastboot you can manually replace every partition this way. including /recovery.
just an idea.
Click to expand...
Click to collapse
Thanks for the idea just got my new phone still got the old one so I'm definitley gonna try some things now. Before I root the new one is there any info or anything someone might want from it. I don't know if it can help someone but it might. I'll wait till tonight to do it
Avalaunchmods said:
go to cyanogens wiki page. and find where he manually replaces the /radio partition.
if you have fastboot you can manually replace every partition this way. including /recovery.
just an idea.
Click to expand...
Click to collapse
Sweet link bro!
Related
I have tested the rooting of the G1 with the CRC1 update (with my boss`s phone ) He accidently got the update and installed it yesterday on his non-rooted G1 and while we were at work tonight we flashed it back down to the RC29 with NO troubles at all ... only thing left to do was download the spl and the recovery image and type telnetd, download telnet connect to local host, and run some script... which all should work just fine since it did let us downgrade. I havent seen anyone here or on google that has tried that yet so I wanted to let everyone know it will let you downgrade to the lower version.
Now if you have a rooted phone and install the update .. you will more than likely loose the root .... but you should be able to get root back by re-rooting the phone and going with a non CRC version until a modified image comes out.
OK we finished the rooting today and it flashed with the new ROM and everything. It now is on the JF1.51MOD with the updated radio.
Yup, read this post:
http://forum.xda-developers.com/showthread.php?t=538536
and this post:
http://forum.xda-developers.com/showthread.php?t=538456
/Close
andonnguyen said:
yup, read this post:
http://forum.xda-developers.com/showthread.php?t=538536
and this post:
http://forum.xda-developers.com/showthread.php?t=538456
/close
Click to expand...
Click to collapse
NEITHER of these 2 threads say anything about anyone testing or confirming that you can downgrade FROM CRC1 and get root again.... the JF thread is saying pretty much dont install it and if you do it wont update anyhow. The other thread was cyogen making an altered CRC1 version that has been patched for updating.
Still no threads like this one that I found
/OPEN
Strapt said:
until a modified image comes out.
Click to expand...
Click to collapse
Which JF will come out with, as posted in my previous post, but good to know that its still downgradable (is that even a word?) to RC29. This thread should be posted in the general Dream section BTW, as its not pertaining to any development topics.
/CLOSE
LULZ.
andonnguyen said:
Which JF will come out with, as posted in my previous post, but good to know that its still downgradable (is that even a word?) to RC29.
Click to expand...
Click to collapse
ya which will be nice when he does come out with it so people can run the phone with that version .. but this inst about who is going to be comming out with a modified image to KEEP root access ...This is to rest peoples fears about NOT being able to re-root the phone if they accept the CRC1 update or not able to root it in the first place... which no one has seemed to have tried/confirmed until now. and .. downgradeable a word?..well ... it is now!
Strapt said:
ya which will be nice when he does come out with it so people can run the phone with that version .. but this inst about who is going to be comming out with a modified image to KEEP root access ...This is to rest peoples fears about NOT being able to re-root the phone if they accept the CRC1 update or not able to root it in the first place... which no one has seemed to have tried/confirmed until now. and .. downgradeable a word?..well ... it is now!
Click to expand...
Click to collapse
So yeah I'm just upping my post count now since I'm bored. lol. Mmm, family guy is funny.
Strange...as far as I know, I have been able to downgrade to RC29 from all official releases, RC30, RC33 and 1.5, since I have had 4 separate G1's since initial release (I'm extremely clumsy and rough with my phones sometime - usually halfway through a bottle of scotch).
Hmm.
Nevermind - apparently alcohol also affects my ability to read thoroughly.
so,here's what I did, I accepted the cr1 update on my stock 1.5 stock g1,
then, I downgraded to RC29 with no problems at all, I also followed the instructions and rooted my phone ( apparently ), after that, I tried to flash a few different roms, but none would load, my g1 will always freeze at the G1 screen, until I install back the stock rom again,
am I doing something wrong?
'cuz am not that new at this, and I feel stupid.
There was never any question of it.
The only firmware known to be easily rooted is RC29.
Downgrading to RC29 is completely independent of what firmware version is actually ON the device -- it is strictly related to SPL version. Since CRC1 is an OS update and NOT an SPL update, it can't possibly have any affect on whether or not you can downgrade to RC29, hence it definitely CAN still be rooted when CRC1 is installed.
funny...
i was at a friends house last night and he wanted me to root his g1. i was there for hours trying to figure out why i couldnt get the bootloader screen to switch to grey. I downloaded DREAIMG.nbh from several sources with several different sdcards. i even have a dedicated card i named ROOTER with all the neccessary files and updates but couldnt get nothing cooking.
el_plebillo said:
so,here's what I did, I accepted the cr1 update on my stock 1.5 stock g1,
then, I downgraded to RC29 with no problems at all, I also followed the instructions and rooted my phone ( apparently ), after that, I tried to flash a few different roms, but none would load, my g1 will always freeze at the G1 screen, until I install back the stock rom again,
am I doing something wrong?
'cuz am not that new at this, and I feel stupid.
Click to expand...
Click to collapse
what ROM are you going to?? if its Hero you HAVE to have the latest spl. If it has autoappsstosd you need to have your sdcrd partitioned right (fat32 first and then ext2) I recommend using the sdsplit method.
oneG said:
funny...
i was at a friends house last night and he wanted me to root his g1. i was there for hours trying to figure out why i couldnt get the bootloader screen to switch to grey. I downloaded DREAIMG.nbh from several sources with several different sdcards. i even have a dedicated card i named ROOTER with all the neccessary files and updates but couldnt get nothing cooking.
Click to expand...
Click to collapse
hmm intersting .. the only time I have seen that is if someone was placing the entire.zip file on the sd card instead of just the DREAMING.nhb file on there. I would just reformat the card to fat32 and place that file only on it again and then try it again and see if anything goes different. Dont know if it makes a difference but i got the DREAMING.nhb off the how to root the g1
Strapt said:
I would just reformat the card to fat32 and place that file only on it again and then try it again and see if anything goes different. Dont know if it makes a difference but i got the DREAMING.nhb off the how to root the g1
Click to expand...
Click to collapse
Yeah that was my initial reaction but to no avail. Like i said earlier, i tried dl the img. from several sources.
Anyway he's not that into his G1 as much as we here are and like my g/f, despite the many features its capable of, only uses it for calls and text. He's excited about tethering tho but kinda paranoid with all that could go wrong like bricking and all that, so yesterday he was a little reluctant for a second attempt due to the day before's problematic flash. I did happen to get his phone to start ringing again without the call going stragiht to voicemail and the lock screen works now, which was the real reason i was over there in the first place.
But as far as root and CRC1 go, i might sneek my g/f's G1 away so i can test there
oneG said:
Yeah that was my initial reaction but to no avail. Like i said earlier, i tried dl the img. from several sources.
Anyway he's not that into his G1 as much as we here are and like my g/f, despite the many features its capable of, only uses it for calls and text. He's excited about tethering tho but kinda paranoid with all that could go wrong like bricking and all that, so yesterday he was a little reluctant for a second attempt due to the day before's problematic flash. I did happen to get his phone to start ringing again without the call going stragiht to voicemail and the lock screen works now, which was the real reason i was over there in the first place.
But as far as root and CRC1 go, i might sneek my g/f's G1 away so i can test there
Click to expand...
Click to collapse
lol ya you should take her and try ... I finished rooting my boss`s CRC1 yesterday. after flashing the .nhb file we added the JF1.51MOD thats found on lucids page .. mainly because it has the radio and the rom in one update. But anyhow he has a rooted G1 straight from CRC1 ... wonder what radio you guys had on that phone and if it needed to be updated before going to the ROM you chose
I needed this!
I needed to root a friends phone. He just bought it, and it had RC29. By the time he got to me, it was CRC1. Regardless, I found this post which showed it worked.
I flashed RC29, Then rooted it. Flashed latest radio, CM 1.4 Recovery, then JF1.50, and finally CM 3.9.7.
It worked beautifully! Thanks for the confirmation post!
SoTacMatt said:
I needed to root a friends phone. He just bought it, and it had RC29. By the time he got to me, it was CRC1. Regardless, I found this post which showed it worked.
I flashed RC29, Then rooted it. Flashed latest radio, CM 1.4 Recovery, then JF1.50, and finally CM 3.9.7.
It worked beautifully! Thanks for the confirmation post!
Click to expand...
Click to collapse
You are very welcome!! Thats why I posted it to let people know that they werent screwed when/if they got the Crc1 update. Glad that it went well for you!
I just got a g1 (and use linux since 1999), and LOVE this phone...sofar.
i would want to root it, and plan to.
i have the 1.5 firmware, and crc1 and am planning this on saturday.
is there a way to take screen shots of it all ? (from the phone)
any tips/ links etc is appreciated.
"run linux, stay happy".
Bellevue Washington
doing the root in Kirkland
Pizza or soda (or beer) on me.
File 1 http://android.clients.google.com/packages/ota/tmobile_opal/894fb8631db9.hboot-1.33.0013.opal.zip
File 2 https://android.clients.google.com/...59adc603a3.signed-opal-ota-60505.e059adc6.zip
File 3 (Still Not sure what this file is)
https://android.clients.google.com/...17d.signed-opal-FRG83-from-DMD64.e3671133.zip
Here are the correct downloads. This update only works on the Original My Touch 3G. Not the My Touch 3G 3.5 or Fender Version.
I took these instructions from Smapdi's Post
Renamed 894fb8631db9.hboot-1.33.0013.opal.zip to update.zip and placed it into the root of my SD card. Rebooted into recovery and flashed it (Turn on with Home then Power Key to boot into recovery). The process restarted the phone a few times (DO NOT TOUCH THE THING ONCE YOU START THE FLASH!!!!!) and eventually booted into 1.6.
I rebooted into fastboot and saw HBOOT was now 1.33.0013 :-D
I then took e059adc603a3.signed-opal-ota-60505.e059adc6.zip and renamed it to update.zip and put it into the root of the SD card deleting the previous file. Repeated the same steps as before and the phone did the whole restart itself a few times thing and eventually booted to 2.2!!!
Great work guys!
Thanks for everyones help I hope you enjoy Froyo 2.2.
Stingerrray
Stingerrray said:
File 1 (I Think) https://android.clients.google.com/...17d.signed-opal-FRG83-from-DMD64.e3671133.zip
File 2 (I Know) https://android.clients.google.com/...59adc603a3.signed-opal-ota-60505.e059adc6.zip
The downloads worked for me can someone confirm that theses are the correct files. And maybe help with installation.
Thanks "Phateless"
Stingerrray
Click to expand...
Click to collapse
I do concur, the Philly Cheese Steak is quite delicious, however I find that nothing beats a good Cheeseburger!
Which one is which?
And do they need to be flashed in a specific order?
File one is new. File 2 is the one that has been out for a couple of days. I'm not sure on the install will test soon.
Stingerrray said:
File one is new. File 2 is the one that has been out for a couple of days. I'm not sure on the install will test soon.
Click to expand...
Click to collapse
ill go ahead and test this aswell, so tech i should flash file 2 then file 1 since that is the order they were released in?
Foo_Blyat said:
ill go ahead and test this aswell, so tech i should flash file 2 then file 1 since that is the order they were released in?
Click to expand...
Click to collapse
actually the I believe the first file is the spl and would be flashed first. Be careful.
XfooYen said:
actually the I believe the first file is the spl and would be flashed first. Be careful.
Click to expand...
Click to collapse
i thought file 1 should be flashed first aswell but to me it looked like the 2.2.1 update since theres a "FRG84-from-DMD64" line in the code.
anyone else care to maybe back that assumption up or throw in your own 2 cents, wouldnt mind a few opinions before i flash these files.
Both downloaded, both have been put onto the root of my sdcard. Just waiting on a guiding light before i boot into stock recovery and flash
I also have the files ready but I dont have the guts to flash. I barely use the MT3G lately but I dont want to risk a brick.
negative
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
has anyone tested these file yet with success?
PulldOvr said:
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
Click to expand...
Click to collapse
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
PulldOvr said:
Good news is the phone doesn't brick after trying to flash the first file. Bad news is it comes across an error. Apparently this is for a different phone. I got the error "E:Error in /sdcard/update.zip (Status 7)" with a bunch of other gibberish about buildprops before it ..
hope this helps someone ..
Click to expand...
Click to collapse
I got the same error message and installation aborted. I tried file #2 first. Rebooted and went back to normal. Mytouch 3g stock.....
Same thing happened when I flashed #1 .....
Foo_Blyat said:
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
Click to expand...
Click to collapse
Before you continue being an ass had you thought about he is someone that upgraded from a mytouch 3g to a vibrant and still has his old mytouch? That is exactly what I did and I am still trying to update my mytouch.
Foo_Blyat said:
if your sig is correct, you are in the wrong forums, no **** its "apparently for a different phone"
Click to expand...
Click to collapse
My Vibrant runs off MT3G roms ...
On a serious note .. I have an original MyTouch 3g, a Cliq, a G1, and a Vibrant ... usually just lurk around these forums and try not to intervene too much because people are quick to become trolls on this site .. then they complain when no one will help them .. gee i wonder why ... learn to be a little nicer, and maybe we can get some work accomplished as a whole ...
and just to clarify, I tested this on an original MyTouch 3g, 1.33.006 SPL, (stock) and unrooted DMD64 build.
This made me think that a "...*** from DMD646" update file would work. I'll be sure to keep my testing to myself so i can avoid trolls like you.
Don't get your panties in a bunch...
I already tried 1.5 -> 2.2.1 and both builds of 1.6 -> 2.2.1, doesn't work in any order
I've tried to update with both files no luck. They are definitly part of the update. I did notice from an earlier post with photos that one file was looking to the system cache file for the other file. So just a thought maybe both files need to be in place before the update can take place. Maybe this could be the problem. Any thoughts on this?
Stingerrray
Sent from my T-Mobile G2 using XDA App
I thought that the first update was supposed to be 300-400kb? Where did you discover this link out of curiosity?
I saw the file name in another post with a view of a botched upgrade due to root. put the file name in the url for the other update and it was a valid url.
Sting
Sent from my T-Mobile G2 using XDA App
The post was here.
http://forum.xda-developers.com/showpost.php?p=8687201&postcount=175
First off any time you want to test if a file is legit or not ( coming from htc/google ) you can just test the keystore via command prompt if the java development kit and runtime is in your system path. Don't remember the code off hand.
Second I would really suggest either using someone elses update script or at least replace/delete most of it. As well as install su and busybox. Because it won't run in a custom recovery.
Enjoy if you can!
so a buddy of mine rooted his wifes eris, and sorta messed up the root, he can get to clockwork mod and all, BUT any rom he tries to flash will say error at line 9 or line 6 not enough space on device, aborting operation....
he also failed to make an nand back up so basically we are stuck in clockwork
someone help! how do we either fix this to flash a rom or unroot/return to stock this device??
we have tryed the RUU method but it doesnt reconize the drvice because we are in clock work
and we have try the pbm img but s=on so were locked out
If s=on then i dont think he got root
Cyostrife said:
If s=on then i dont think he got root
Click to expand...
Click to collapse
he followed the method on theunlockr.com
worked just fine for his eris, but his wifes is giving said errors...
with just bootloader and cwm avalible what can we do to fix this?
mytouchguy said:
he followed the method on theunlockr.com
worked just fine for his eris, but his wifes is giving said errors...
with just bootloader and cwm avalible what can we do to fix this?
Click to expand...
Click to collapse
How full is the battery? I get errors if I try to flash and the battery is ~30% or less.
lp4261 said:
How full is the battery? I get errors if I try to flash and the battery is ~30% or less.
Click to expand...
Click to collapse
not sure, i was doing a remote help, i do alot of rooting for tmo phones ive just never seen this error... i plan to go help him in person just trying to get some advice
will it still charge with no rom? if so ill have him charge it overnight
mytouchguy said:
not sure, i was doing a remote help, i do alot of rooting for tmo phones ive just never seen this error... i plan to go help him in person just trying to get some advice
will it still charge with no rom? if so ill have him charge it overnight
Click to expand...
Click to collapse
I would assume so, but I'm still a novice. I just noticed this from my own experience.
lp4261 said:
I would assume so, but I'm still a novice. I just noticed this from my own experience.
Click to expand...
Click to collapse
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
mytouchguy said:
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
Click to expand...
Click to collapse
if u can power the device on , i believe it aint bricked
Can he get to hboot and usb from there. if so let me know and also can he get to recovery...
Sent from my froshedyo using XDA App
mytouchguy said:
what type of errors have you seen?
his says not enough space on device... could this relate the cwm bricking devices?
more so is the device bricked at this point or are we still ok?
Click to expand...
Click to collapse
That sounds like the type of stuff i would get. that or a push file via adb thing. It doesn't sound like a clockwork bricking. The problem with CWM is that it doesn't have the verification step that amon-ra does. Are you flashing roms from these forums? I trust the devs here, but I don't think I would flash a rom that isn't from here w/o a recommendation from one of the devs. I would plug the phone in and let it go for a bit and try again after it has a charge.
lp4261 said:
I would assume so, but I'm still a novice. I just noticed this from my own experience.
Click to expand...
Click to collapse
tazzpatriot said:
if u can power the device on , i believe it aint bricked
Click to expand...
Click to collapse
yes we can power on we can use cwm mod hell we can place a pbmimg on the sd card, it just wont read it because s=on at the time
in doing a massive google search
any chance this would work
http://www.droidforums.net/forum/hacking-help/37717-unroot-unbrick-using-sbf-post-ikithme.html
if not anyone got any ideas?
3 more questions
a: is there a way to get s=off without android loaded, between just the bootloader and cwm avalible? this way we can hopefully just use the pbmimg
B: is there a way to replace cwm with amon ra in this current state to use flashback21? http://forum.xda-developers.com/showthread.php?t=792026
and this is a really crazy thought but can we take the backup we created tonight from his eris... both phones are EXACTLY alike, purchased at the same time and all...and use it to flash in cwm to recover the dead phone?
there is way to flash S=OFF through recovery. Flash the file from here..
In order to use a nandroid from a different phone you need to change a few things to make it work. I read it somewhere. If I find it ill let ya know
Sent from my KaosGingerbread using XDA App
CCCP4ever said:
there is way to flash S=OFF through recovery. Flash the file from here..
Click to expand...
Click to collapse
This is only supposed to work if you have bootloader version 1.49. If you're lucky like me and have 1.47 it won't work. That's according to bftbo. He's tried both.
lp4261 said:
This is only supposed to work if you have bootloader version 1.47. If you're lucky like me and have 1.49 it won't work. That's according to bftbo. He's tried both.
Click to expand...
Click to collapse
ill have this on standby, idk what bootloader he has we kinda gave up for the night
erismaster said:
In order to use a nandroid from a different phone you need to change a few things to make it work. I read it somewhere. If I find it ill let ya know
Sent from my KaosGingerbread using XDA App
Click to expand...
Click to collapse
awesome ill do a little looking myself and see, but thanks. figured it was a crazy but possible idea
mytouchguy said:
ill have this on standby, idk what bootloader he has we kinda gave up for the night
Click to expand...
Click to collapse
here's bftbo's answer to my question:
http://forum.xda-developers.com/showpost.php?p=10501766&postcount=69
within moments i found this...
anyone know how to achive this? both phones in this instance are the droid ERIS
http://androidforums.com/incredible...ansferring-nandroid-backup-another-phone.html
lp4261 said:
here's bftbo's answer to my question:
http://forum.xda-developers.com/showpost.php?p=10501766&postcount=69
Click to expand...
Click to collapse
any way to roll back the bootloader as he mentioned in the event that he has 1.49?
and this is a really stupid question , but im so brain fryed... how do we check his bootloader version?
So I've apparently, effectively bricked my phone. Under bootloader it is listed as S-OFF. Is there any way I can return my evo in and stay under warranty?
Note: I can not reach recovery.
What happens when you rename a recovery to PC36IMG.zip and try to update via bootloader?
I go into a boot loop no matter what i do, no matter what I flash. I have flashed 10+ PC36IMGs with everything from bootloaders to recoveries, to every img that can be on the phone... there is a thread still on the first page if you want to look at that.
Anyways, it doesn't look like I'm going to be able to fix it, so this is more about what options are available to me in getting a new phone, if you having any suggestions though on what I can do to fix mine, please be my guest and comment on my thread below, I'm still trying to fix it!
Just report the phone lost or stolen and pay $100 deductible.
Sent from my PC36100 using XDA App
I would try one last time to flash Amon's recovery.
Download this: http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
Rename it to "PC36IMG.zip"
put it on the root of your sd card via a card reader if you have one or someone elses phone.
then update via bootloader.
Other than that I'm out of ideas. The good news is I'm not as savvy as 95% people on here, which means someone much smarter than me might know the answer. Good luck.
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
thanamesjames said:
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
Click to expand...
Click to collapse
i dont think its a warranty thing its insurance and i think your screwed
What happens when you put a pc36img.zip file on the root of your SD card and start up in bootloader?
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
So you cleared all the caches?
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
I've done "clear storage" I don't see a place to clear anything other than that in hboot.
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
Pretty much. If you haven't tried yet, try re-rooting via toast's method.
http://forum.xda-developers.com/showthread.php?t=690762
Try going through the whole process. If successful make sure you have a nice stock ROM like the current Sprint Lovers ROM to flash.
Unfortunately my phone isn't getting listed as a device under adb, and thats part of the toast tutorial I have tried his eng-PC36IMG.zip, and it didn't work
woah woah woah....
take your phone to wal-mart and slide it over the demagnetizer at the register a couple times.
THAN take it in.
_MetalHead_ said:
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
Click to expand...
Click to collapse
I had nightlies of CM7 they would reboot fairly often, but I just figured they were unstable. Out of nowhere it rebooted, and lost all my texts, and desynced my google account. I decided to switch to CM6. When i switched to CM6, soon after it rebooted out of nowhere, and then staid in an endless loop and never came out. I currently have hboot .76, for more fastboot commands.
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
_MetalHead_ said:
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
Click to expand...
Click to collapse
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
thanamesjames said:
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
Click to expand...
Click to collapse
Yep :/ I don't know what to tell you then man, sorry.
I guess I'm going to Sprint and playing stupid!
Has anyone done this successfully?
It sucks because as soon as I started having these problems, all the experts would be frustrated and say "*sigh* you're not bricked, you can get into bootloader" and so I was so sure it was fixable... but apparently not. Every time I mention it I have a thousand people yell at me "FLASH PC36IMG!!" Anyways thanks for the help!
Ok so I just tried to get the 3.1 update from the XOOM pushed to my tablet and well it bricked me so dont try this if a few people r wanting this just wait for the 3.1 update later this year.
ouch, so what are you gonna do now, can u fix it?
dc13 said:
Ok so I just tried to get the 3.1 update from the XOOM pushed to my tablet and well it bricked me so dont try this if a few people r wanting this just wait for the 3.1 update later this year.
Click to expand...
Click to collapse
Can you tell us where you get the update file? Can you share it?
Also, how you flash the file? Through recovery?
Can you describe the 'brick' situation? Boot loop?
Finally, how are you going to restore back to original?
Thanks a lot.
He should be able to nvflash back I'd think.
muqali said:
He should be able to nvflash back I'd think.
Click to expand...
Click to collapse
nvflash isn't working for us atm
I think that he can use a stock update.zip and flash it through recovery.
ardatdat said:
Can you tell us where you get the update file? Can you share it?
Also, how you flash the file? Through recovery?
Can you describe the 'brick' situation? Boot loop?
Finally, how are you going to restore back to original?
Thanks a lot.
Click to expand...
Click to collapse
No I'm not going to share a update that will brick ur tablet.
Boot look at the Android. I know Im bricked.
I'm just going to return it and get my money back and ill wait a little bit.
There is NO NVFlash
I can use the Chinese update.zip but id rather not
dc13 said:
No I'm not going to share a update that will brick ur tablet.
Boot look at the Android. I know Im bricked.
I'm just going to return it and get my money back and ill wait a little bit.
There is NO NVFlash
I can use the Chinese update.zip but id rather not
Click to expand...
Click to collapse
You could flash the chinese thing.. try to flash my recovery and if it doesn't work just use dd to flash the recovery from china again
seraphimserapis said:
nvflash isn't working for us atm
Click to expand...
Click to collapse
Hadn't been following our support too closely. I just assumed it worked on all tegra tabs equally. God what I wouldn't give for tabs to be like PCs.
Use the chinese update.zip
Its not bad... I had to use it because I was fooling around too much and crashed with no reboot in sight. I used SYSTEMAPP REMOVER to disable all the chinese apps and root explorer to delete the old files in /system/app then rebooted.
Also, you can add the marketplace through the /system/app just enable read/write and there is no need to push through ADB!!! it will give you error once, rewrite over the files again, re-install, and re-start and voila... you get the free games from the "GoMarketHD" and you get the MARKET back, granted, its not the HONEYCOMB market but hey, its the market... jejeje