Hi,
A friend of mine said his Amaze 4G just randomly rebooted into bootloader and couldn't get out so he came to me. This Amaze 4G is completely stock and was never rooted before. I had a hard time believing this until I saw the device (which I have with me right now). It really is stuck in the bootloader. I tried hitting factory reset and clear storage in the bootloader option and all it did was reboot back to bootloader. I tried to HTC Dev unlock, but I can't even run the fastboot command to get the device keys (yes I do have the drivers installed). Any way to solve this. I tried searching the Googles and nothing like this came up sooooo. I have the tools to do pretty much anything just send me the links to what I would need to fix this. My friend needs a phone to use lol... Thanks.
EDIT: I can run Image CRC though. Values in box below.
Code:
rpm: 0xFA0A9E93
sbl1: 0bB33AFDC0
sbl2: 0xD50B8AD
sbl3: 0xA1B5642F
tz: 0x22B51D2E
radio: 0x63CCF02C
hboot: 0xE8505494
boot: 0xE0B6D1C4
recovery: 0x59425AFD
system: 0xE9F6F87F
Try and download the stock ruu rename it to PH85IMG.zip and put it on ya root of the SD card then see what happens
Sent from my HTC_Amaze_4G using xda app-developers app
Carrier?
Original rom? (ics/gb)
Is the phone from the Asia region? (India packistan etc?)
Sig:
What do you mean I can't say that??!!.. It's the fkin Internet!
That's a question to ask ya friend
Sent from my HTC_Amaze_4G using xda app-developers app
---------- Post added at 01:44 AM ---------- Previous post was at 01:41 AM ----------
What's the bootloader number saying if its the 1. 92 that's asian
Sent from my HTC_Amaze_4G using xda app-developers app
Its a T-Mobile US one. Probably should have mentioned that in OP. Anyways tried with stock zip renamed to PH85IMG and it didn't seem to work. It loaded up the zip but still rebooted into boot loader. It might be that it doesn't have enough of a charge so I'm just going to leave it in for a while then try again.
Edit: Okay tried it again. It got through checking but didn't do anything. When I rebooted it got to this black screen with a half green android logo. Then rebooted back into boot loader. It was also originally on ICS.
Sent from my Nexus 4 using Tapatalk 2
That's the recovery logo is that the stock t-mobile ruu and u sure ya fren. Didn't try to s-off
Sent from my HTC_Amaze_4G using xda app-developers app
Nope. He said he woke up and it was like that. He's not really one of those people who tinkers with their phone. I checked the MD5 just in case and it matched. Trying again. Almost ready to tell him to take to a T-Mobile store even though there isn't any around.
Sent from my Nexus 4 using Tapatalk 2
Use a OTA T-MOBILE ZIP
Sent from my HTC_Amaze_4G using xda app-developers app
daorderdillon said:
Use a OTA T-MOBILE ZIP
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
Just tried the one from the collection thread and it didn't work. Rebooted straight into boot loader again.
Edit. Attached pics of screen I'm stuck on and can't get out of. Also whenever I try to run any fast boot command I get a status malformed error.
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Nexus 4 using Tapatalk 2
SOMETHING DEFINITELY WRONG. THEN
Sent from my HTC_Amaze_4G using xda app-developers app
Sounds to me like all of the partitions somehow got erased from the phone for the recovery or somethin
aj_2423 said:
Sounds to me like all of the partitions somehow got erased from the phone for the recovery or somethin
Click to expand...
Click to collapse
So how would I fix that if I can even fix that?
Just thought of using fast boot to flash everything but I don't think it would work since it is S-ON.
Edit: Tried anyways. Signature failed as expected.
Sent from my Nexus 4 using Tapatalk 2
stab244 said:
So how would I fix that if I can even fix that?
Just thought of using fast boot to flash everything but I don't think it would work since it is S-ON.
Edit: Tried anyways. Signature failed as expected.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
If it wont take an RUU then im not sure there is much that you can do
Not that i know of anyway
just my opinion..when i fail S off for the 1st time same happened to me very same..try to flash 4ext from hasoon's AIO ?? if it work then flash a stock rom through smart flash...that worked for me
He can't flash nothing cuz. He is not unlocked and rooted and his fast boot don't work
Sent from my HTC_Amaze_4G using xda app-developers app
Looks like you'll have to do some research via adb.
With adb you can see the file structure etc..
No file structure but a positive connection means your phone has something funny happening..
Hassoon's kit does things via adb scripts (Automated adb commands)
It only has so many commands to keep it simple and clutter free..
Adb is also capable of forcing things to the phone.. Some of these capabilities are not in Hassoon's kit for good reason..
Your probably fine but it will take some research
Sig:
What do you mean I can't say that??!!.. It's the fkin Internet!
---------- Post added at 09:28 AM ---------- Previous post was at 09:19 AM ----------
Looks like you'll have to try to go all the way to Soff & super cid
Sig:
What do you mean I can't say that??!!.. It's the fkin Internet!
Well my friend left and I gave his phone back to him so I can't really do anything right now. Gonna go look and see if there is a way to S-OFF without using HTC Dev since their method doesn't work.
Sent from my Nexus 4 using Tapatalk 2
Related
Hey guys, been awhile since I've been on XDA.
Rode the iOS bus for awhile.
Long story short I went and bought a i-777 earlier today and I did a factory reset via the settings menu then proceeded to do a hard reset to clean the phone out.
I pressed and held the volume down button and pressed and released the power button. A warning about a custom OS popped up and I proceeded and it took me into a screen that said "Odin" at the very top.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, I bought this phone through a second hand electronics store and I'm wondering if this phone has been improperly rooted and I just picked up someone else's headache.
If that's the case I plain on returning it.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
You about phone screen looks like the phone has stock Gingerbread installed. UCKK6 was the update version. The phone originally shipped with UCKH7. Yours may have been updated over the air, or later models were shipped with UCKK6.
I've never heard of the button configuration that you describe for this phone. I tried doing the same thing, holding down vol- and short press the power button, but the phone just booted normally. But then I am running a custom ICS rom.
Boot the phone into download mode: with the phone off, hold both volume buttons, but not power, and plug in the usb cable. When you get the warning screen, use the volume up button to go to the download screen. Look at the flash counter information at the top of the screen. That will tell you if the phone has been modified. (Unless they followed my guide on flashing custom firmware without incrementing the flash counter, lol.)
Even if the phone has been modified, that doesn't necessarily mean it has been damaged.
"Odin Mode
Product name: sgh-1777
Custom binary download: no
Current binary: Samsung official"
Is what I'm looking at, then it has Andy and "downloading....do not turn off target!!"
I just wana make sure that is what I'm supposed to see..
bdpyo said:
"Odin Mode
Product name: sgh-1777
Custom binary download: no
Current binary: Samsung official"
Is what I'm looking at, then it has Andy and "downloading....do not turn off target!!"
I just wana make sure that is what I'm supposed to see..
Click to expand...
Click to collapse
Your phone appears to be stock and to have never been modified. What you are seeing is exactly what would be expected of a phone right out of the box.
Good Odin threw me off.
My other problem is now I'm rooted with broken wifi, running around I'm circles trying to figure this one out. :/
Tried flashing cm7 stable with no success to rid of this stock rom and modified kernal that provides root access.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
bdpyo said:
Good Odin threw me off.
My other problem is now I'm rooted with broken wifi, running around I'm circles trying to figure this one out. :/
Tried flashing cm7 stable with no success to rid of this stock rom and modified kernal that provides root access.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Broken WiFi? Sounds like u went to galaxys2root.com and downloaded some garbage from zedomax but I'm hoping I'm wrong
Sent from my SGH-i777 using XDA
LOL. I wish you were wrong as well, lack of patients got to me and it was a quick way to.get root access.
Just read about a kernal cleaning script that I hope works.
And I read that rom manager sucks too. Yikes the times have changed.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
bdpyo said:
LOL. I wish you were wrong as well, lack of patients got to me and it was a quick way to.get root access.
Just read about a kernal cleaning script that I hope works.
And I read that rom manager sucks too. Yikes the times have changed.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Just flash a ROM and u should be fine
Sent from my SGH-i777 using XDA
Thanks.for replying Brandon but I'm not able to flash anything via. Cwr
Starts to flash then fails signature check..
Any other insight?
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
bdpyo said:
Thanks.for replying Brandon but I'm not able to flash anything via. Cwr
Starts to flash then fails signature check..
Any other insight?
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Ur using rom manager aren't u? Don't use rom manager. Use cwm recovery
Sent from my SGH-i777 using XDA
brandonarev said:
Ur using rom manager aren't u? Don't use rom manager. Use cwm recovery
Sent from my SGH-i777 using XDA
Click to expand...
Click to collapse
No I've been trying in recovery only. I used my PC earlier to download cm7 then moved it to my phone.
Wipe/factory reset
Wipe cache
Wipe Dalvik
Then proceed to flash ROM and get some kind of a signature failure..
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
bdpyo said:
No I've been trying in recovery only. I used my PC earlier to download cm7 then moved it to my phone.
Wipe/factory reset
Wipe cache
Wipe Dalvik
Then proceed to flash ROM and get some kind of a signature failure..
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Downloading their "unroot" tar now to flash in Odin, which should put me back on 2.3.4 which I beleive the original root method was designed for.
Once back on 2.3.4 im going to try and re-root and see how it goes from there, hopefully I can resolve this with out going through extreme mesaures. See kids, this is perfect example of "I didnt take my time to read and reseach before I started pushing buttons." LOL
I just wanna run CM7 dammit!
bdpyo said:
Downloading their "unroot" tar now to flash in Odin, which should put me back on 2.3.4 which I beleive the original root method was designed for.
Once back on 2.3.4 im going to try and re-root and see how it goes from there, hopefully I can resolve this with out going through extreme mesaures. See kids, this is perfect example of "I didnt take my time to read and reseach before I started pushing buttons." LOL
I just wanna run CM7 dammit!
Click to expand...
Click to collapse
Why CM7 and not cm9/aokp?
Sent from my SGH-I777 using Tapatalk 2
I like CM7 a hair better then CM9.
In other news, flashed another kernal via Odin and got my wifi and and flashing capabilities back, flashed cm-7.2.0 now waiting at the splash screen
EDIT: I got it up and running, seems that the original kernal just screws up everything.
Thanks guys
bdpyo said:
EDIT: I got it up and running, seems that the original kernal just screws up everything.
Thanks guys
Click to expand...
Click to collapse
Yes, zedomax kernel screws over a lot of people. Wish there were some way to warn unsuspecting folks. Actually, the zedomax unroot causes more problems than the rooting kernel.
Glad you've got everything going. Now, just read a few minutes every day, and before long, you'll be up to speed.
Well glad I didn't unroot then. Lol
Got cm7 running like the old days, used to have a aria, captivate, inspire and nexus s. Feels good to be back.
Sent from my SGH-I777 using xda app-developers app
Hi,
I plan to order a Verizon S4 phone today.
When it arrives, I will try to root it right away.
Will probably turn it on in a bad signal area (my basement) and turn on airplane mode.
I have never owned a Samsung phone before.
How can I check if the phone came from Verizon with the OTA already installed?
Thanks,
Howard
You want it to say baseband..... Mdk, build...... Mdk. Not me7.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I545 using xda premium
If you installed the update then you have the update. Real simple folks.
...sent from my SCH-I545 ME7 Rooted using xda app-developers app
You have it!
You have the new update!
I made the mistake of installing it!
Ryno77 said:
You want it to say baseband..... Mdk, build...... Mdk. Not me7.
View attachment 2113534
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
My new phone will arrive tomorrow.
I plan to just immediately boot it into Odin mode, and start the rooting process.
Is there a simple way to see if it has MDK while in Odin mode.
I just booted into Odin mode and it does not say what baseband your on. I would follow the rooting process and if flashing the prerelease kernel fails then you know it's a updated phone.
Sent from my SCH-I545 using xda premium
Ryno77 said:
I just booted into Odin mode and it does not say what baseband your on. I would follow the rooting process and if flashing the prerelease kernel fails then you know it's a updated phone.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Thanks
Howard
Worked out great.
I did NOT put in the SIM card.
Did everything using WiFi.
The rooting process worked.
I am on baseband I545VRUAMDK with root and TWRP recovery installed.
Used Titanium Backup to freeze SDM
I still have not inserted the SIM card.
HowardZ said:
Worked out great.
I did NOT put in the SIM card.
Did everything using WiFi.
The rooting process worked.
I am on baseband I545VRUAMDK with root and TWRP recovery installed.
Used Titanium Backup to freeze SDM
I still have not inserted the SIM card.
Click to expand...
Click to collapse
Nice! Glad it worked out for you!
Sent from my SCH-I545 using xda premium
Another related question regarding rooting:
I installed CleanRom, and when booting up it asks me about "update samsung device" which starts a download.
I assume I should always say NO - as this might be the dreaded ME7 update which eliminates root and locks the bootloader ????
I would say no. It's weird that your getting that with a custom rom installed. Can you get a screen shot of the pop up?
Sent from my SCH-I545 using xda premium
Ryno77 said:
I would say no. It's weird that your getting that with a custom rom installed. Can you get a screen shot of the pop up?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
I only get the Samsung direct download via Wifi (no SIM card installed yet) when I use TWRP to factory reset and then boot the phone.
On subsequent reboots, I do not get prompted for the Samsung download.
I have been suffering from the google playstore error 920. This seems to occur at about 100 apps of my 200 apps. I've been TWRP factory reset to start it over again. But, now I've figured out how to get the playstore to resume my 200 apps auto-installation: First, wait 10 minutes, then in settings I remove the google account, reboot to TWRP recovery and wipe cache and dalvic-cache, boot phone, run playstore which prompts me to re enter the google account.
I am trying to set the phone up completely with all my apps, accounts, etc.. before activating the SIM card and installing the SIM card.
Let me know if you really wan tthe samsung update screen shot. If yes, then after I'm done setting the phone up I will make a nandroid backup and do a TWRP factory reset to get you a picture.
Regards,
Nope, was just curious. No need going through extra work.
Sent from my SCH-I545 using xda premium
I am not really sure how to explain what is going on so I made a video to kind of show.
Sorry it is shaky I was holding my camera and trying to use the phone at the same time.
So I did the HTC Unlock Bootloader thing about 2 months ago and I have been stuck with a phone that will not update or anything anymore.
I got fed up with trying to get it to work so I have just been using the phone as is, but it is getting slow and buggy on me so I would like to finish the rooting or get it back to stock or something.
When I boot into recovery as you will see nothing works.
HTC has an update right now on my phone and if I download and go to install the update it reboots into recovery and there is an error saying it could not mount the internal storage or something so update was aborted.
I was hoping someone could watch this video and then point me in the right direction of what to do next.
I tried to get a good shot of the recovery screen so you could see S-ON and the versions n junk.
https://www.youtube.com/watch?v=z2BC1nwo5V4
Thank you guys!
The first problem is CWM does not play nice with the Evo 4G LTE you need to use TWRP.
If you want to take the OTA Update you will need to re-lock your bootloader and install a stock recovery.
bigdaddy619 said:
The first problem is CWM does not play nice with the Evo 4G LTE you need to use TWRP.
If you want to take the OTA Update you will need to re-lock your bootloader and install a stock recovery.
Click to expand...
Click to collapse
^This. You've most likely borked your misc partition with CWM, so you'll need to fix that at some point. As for the rest, you can either do as Bigdaddy says, or install TWRP recovery and flash a ROM.
Sent from my HTC EVO 4G LTE
I downloaded GooManager and attempted to install TWRP. It said it installed but when I rebooted in to recovery it was still using CWM.
Any thoughts on how to force this install? Also when I tried to reboot into recovery using the GooManager app it would not reboot.
I will keep fussing with it and see if I can get TWRP to install.
Oh Bam! I got TWRP working.
Beautiful. I just need to find a ROM to use now..
Psywar28 said:
Oh Bam! I got TWRP working.
Beautiful. I just need to find a ROM to use now..
Click to expand...
Click to collapse
Keep in mind if you're S-on you'll need to install the kernel separately from the ROM. For more info hit the top link in my sig.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Keep in mind if you're S-on you'll need to install the kernel separately from the ROM. For more info hit the top link in my sig.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Thank you! I will attempt to use Moonshine to get S-OFF
I was going to download this ROM would I then just download the S-OFF Version?
I was going to do the S-ON before.
If you're S-on use the S-on version.
Sent from my HTC EVO 4G LTE
FinZ28 said:
If you're S-on use the S-on version.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Moonshine was successful! I am now S-OFF!
Psywar28 said:
Moonshine was successful! I am now S-OFF!
Click to expand...
Click to collapse
Good deal:thumbup:
Sent from my HTC EVO 4G LTE
Ran into an issue.. I was attempting to install CM 11
It has failed on me. Any idea's why?
EDIT: weird note too.. I just went to boot back into the System and TWRP told me I lost Root Permissions.. and it attempted to fix it.. Dunno if it did yet or not.
BAH... Wont reboot back into the System.. Cycles twice and then goes back into TWRP Recovery.
EDIT EDIT: Ok.. So I got some of it fixed.. I ended up getting this Sense 5 ROM installed.. now I am installing this CM 10.2 ROM which seems to be working..
I just can't figure out why CM 11 wont install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Psywar28 said:
Ran into an issue.. I was attempting to install CM 11
It has failed on me. Any idea's why?
EDIT: weird note too.. I just went to boot back into the System and TWRP told me I lost Root Permissions.. and it attempted to fix it.. Dunno if it did yet or not.
BAH... Wont reboot back into the System.. Cycles twice and then goes back into TWRP Recovery.
EDIT EDIT: Ok.. So I got some of it fixed.. I ended up getting this Sense 5 ROM installed.. now I am installing this CM 10.2 ROM which seems to be working..
I just can't figure out why CM 11 wont install.
Click to expand...
Click to collapse
You probably have the wrong twrp for cm11. You need to use the recovery that is in the first post of the cm11 thread. To install it you'll need to do fastboot flash recovery.
You can get it from the first post here
http://forum.xda-developers.com/showthread.php?t=2518211
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
You probably have the wrong twrp for cm11. You need to use the recovery that is in the first post of the cm11 thread. To install it you'll need to do fastboot flash recovery.
You can get it from the first post here
http://forum.xda-developers.com/showthread.php?t=2518211
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah I noticed I do have the wrong recovery for it.
I will attempt to install the one for CM 11..
Any idea why this Sense 5 ROM I am using will make phone calls but will not send any SMS's to anyone? Just keeps saying failed...
I kinda dig this Sense 5 ROM.. I have not been able to figure it out.
EDIT:
Got the new TWRP.img file installed.. I had a hard time doing it in Terminal Emulator so I just downloaded a freaking app that installed custom recoveries.
So it successfully installed CM11.. Now I am sitting here waiting for it to boot up.
I have the logo spinning around and around.. I hate these boot animations cuz I can never tell if it is stuck in a boot loop or if it is just working hard.
So I will give it 15/20mins.. Then I am not sure wtf to do other than go back to Sense 5.. Which I installed for a second time and I still could not get SMS to send or receive.
Glad you got it to boot.
If it's spinning it will probably boot up.
Since you did moonshine you should have been able to install the recovery with fast boot.
It's a good practice to have.
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
Glad you got it to boot.
If it's spinning it will probably boot up.
Since you did moonshine you should have been able to install the recovery with fast boot.
It's a good practice to have.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah CM 11 finally booted up.
I can make phone calls but I cannot send or receive SMS. Same issue I was having with the Sense 5 ROM.
I have been through all the settings I can find and nothing has worked yet.. Any ideas what might be wrong?
Psywar28 said:
Yeah CM 11 finally booted up.
I can make phone calls but I cannot send or receive SMS. Same issue I was having with the Sense 5 ROM.
I have been through all the settings I can find and nothing has worked yet.. Any ideas what might be wrong?
Click to expand...
Click to collapse
After you did moonshine did you make a call on sense and use the self activate feature in settings?
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
After you did moonshine did you make a call on sense and use the self activate feature in settings?
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I did.
When I loaded into the Sense 5 ROM it did not have any of my Profile Information so I could not use the phone with out doing the activation thing.
Psywar28 said:
Yes I did.
When I loaded into the Sense 5 ROM it did not have any of my Profile Information so I could not use the phone with out doing the activation thing.
Click to expand...
Click to collapse
Hmm. I don't know then. I never tried any of the sense 5 ROMs.
Personally at this point I would flash stock rooted, then self activate, update prl and profile, then call sprint and ask them to refresh my connection with them.
Then verify everything works, create a backup of that, and then go back to cm11.
Sent from my EVO using XDA Premium 4 mobile app
NaterTots said:
Hmm. I don't know then. I never tried any of the sense 5 ROMs.
Personally at this point I would flash stock rooted, then self activate, update prl and profile, then call sprint and ask them to refresh my connection with them.
Then verify everything works, create a backup of that, and then go back to cm11.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright sounds like a plan! Not a fun one though haha!!
Thanks for the advise!
Turns out I just needed to update to the latest firmware!
SO Day 1 was pretty smooth. Charged it up. Booted it up. Restored from my backup, ready to test L new back up and restore system. Only to learn, App Data is still not restored. Basically, I'll be using Helium longer. Anyway, I looked for flaws, realized many of them were not present. Willing to work with what was there. Decided I'll keep it. Weight was something to get use to, but knowing the iPad Air 2 is heavier made me feel better.
I even did an impressions video: https://www.youtube.com/watch?v=jscA5nn0B8I
Then, this happened on Day two:
Using it like Day 1. Then the N9 rebooted suddenly. Stuck in a boot loop. Turn off. Try to boot up. Freezes and rebooted. Went into recovery menu. Clear cache. Same result. So decided to give up and went here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hit factory reset. Then it rebooted and boots up with a message at the top This is a developer device and not intended for production use.
No longer can boot the OS. Goes straight to recovery(first screenshot). Tried to flash factory image. But cant unlock the boot loader. Why? I didn't enable OEM unlock in Dev settings. Wow.
So when searching and found one other user. He claims Chrome might be the issue. Which would line up to my theory of Chrome being unoptimized fully for L. Mainly because the device hits over 100F after 5mins of use.
Long story short. I RMA it for a exchange. Guess what I'm sort of asking is, what else can be done? Either way, just wanted to share my experience in case it happens to someone.
Well, here's a third user, lol. In my case, I unlocked it, installed twrp recovery and root, then unchecked OEM unlock option in developer menu and used adb to lock again. Upon reboot, same thing that happened to you happened to me. Have you modified the system at all? At first I thought maybe it was root or the custom recovery that did it, but it seems to not be the case with you and the other user.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 10:13 PM ---------- Previous post was at 10:08 PM ----------
Seems to be no way around this. Can't even wipe anything with adb and can't boot an external boot loader when OEM locked. Ended up getting a repair ticket with HTC. Warranty says it doesn't cover, but seems to affect unmodified systems too do we'll see. I'll update in this thread
Sent from my Nexus 5 using XDA Free mobile app
A browser would not cause a bootloop. It sounds like you have a corrupt system. Have you rooted or flashed anything? Perhaps in fastboot?
ecuzr467 said:
Well, here's a third user, lol. In my case, I unlocked it, installed twrp recovery and root, then unchecked OEM unlock option in developer menu and used adb to lock again. Upon reboot, same thing that happened to you happened to me. Have you modified the system at all? At first I thought maybe it was root or the custom recovery that did it, but it seems to not be the case with you and the other user.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 10:13 PM ---------- Previous post was at 10:08 PM ----------
Seems to be no way around this. Can't even wipe anything with adb and can't boot an external boot loader when OEM locked. Ended up getting a repair ticket with HTC. Warranty says it doesn't cover, but seems to affect unmodified systems too do we'll see. I'll update in this thread
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
richii0207 said:
A browser would not cause a bootloop. It sounds like you have a corrupt system. Have you rooted or flashed anything? Perhaps in fastboot?
Click to expand...
Click to collapse
Nope. Never rooted or flashed anything. It just shut down and boot loop. Either way Amazon sent me a new one.
Did you get to keep the old one?
dasmoover said:
Did you get to keep the old one?
Click to expand...
Click to collapse
No. I request a replacement via Amazon.
Same problem
I got this new nexus 9 and on boot it just says no command, boot loader is locked, I recieved it this way and I am not in US right now so can't claim guarantee or anything, is there anything that I can do to run this thing?
sahirsani said:
I got this new nexus 9 and on boot it just says no command, boot loader is locked, I recieved it this way and I am not in US right now so can't claim guarantee or anything, is there anything that I can do to run this thing?
Click to expand...
Click to collapse
Flash the factory image with fastboot
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Flash the factory image with fastboot
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Is it even possible with locked boot loader, I tried it with nexus toolkit but it tells me operation failed because of locked boot loader.
sahirsani said:
Is it even possible with locked boot loader, I tried it with nexus toolkit but it tells me operation failed because of locked boot loader.
Click to expand...
Click to collapse
Do you have a problem unlocking the bootloader? Just fastboot oem unlock
Sent from my Nexus 9 using XDA Free mobile app
Yap, tried that it tells me that I don't have permission to run this command, it could be because I never was able to get into os and turn developer options on, I can get into recovery and fast boot, but that is all I get, after google logo my screen shows a dead android with no command text.
Sent from my SM-N910C using XDA Free mobile app
Here's a fourth user.
ecuzr467 said:
Well, here's a third user, lol. In my case, I unlocked it, installed twrp recovery and root, then unchecked OEM unlock option in developer menu and used adb to lock again. Upon reboot, same thing that happened to you happened to me. Have you modified the system at all? At first I thought maybe it was root or the custom recovery that did it, but it seems to not be the case with you and the other user.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 10:13 PM ---------- Previous post was at 10:08 PM ----------
Seems to be no way around this. Can't even wipe anything with adb and can't boot an external boot loader when OEM locked. Ended up getting a repair ticket with HTC. Warranty says it doesn't cover, but seems to affect unmodified systems too do we'll see. I'll update in this thread
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
While I usually root a new device as soon as I purchase it, I decided not to until I received the 5.1 update, which has yet to come. This morning a 5.0.2 update was available. I clicked the update and it then got stuck in a bootloop. The bootloader is locked, the developer options are enabled, but the "Allow OEM Unlock" was not ever checked in the Developer options. I can access the HBOOT, FASTBOOT, and Recovery. I did a factory reset, still nothing. I will try to RMA with Amazon as well.
I got the 5.0.2 last night. Since I applied it this morning my Nexus 9 is stuck in a boot loop. (Boot loader locked, stock etc).
Not tried to factory restore yet, but this doesn't sound promising.
Same here
Updated this morning to 5.02, still boot looping since 9 am.... 3,5 hrs.
I hope it will start before hard reset.
Factory reset didn't work for me either, started the RMA process through Google Play. They are sending me a new unit.
My device is also stuck after applying the 5.0.2 OTA (unlocked, unrooted, stock). Tried wiping the cache partition, and it's still hanging. I will try a factory reset next, but I am not very optimistic though. It seems we are not alone -> https://productforums.google.com/forum/#!category-topic/nexus/P6A7S1keMec
Has the 5.0.2 OTA worked for anyone?
adstro said:
My device is also stuck after applying the 5.0.2 OTA (unlocked, unrooted, stock). Tried wiping the cache partition, and it's still hanging. I will try a factory reset next, but I am not very optimistic though. It seems we are not alone -> https://productforums.google.com/forum/#!category-topic/nexus/P6A7S1keMec
Has the 5.0.2 OTA worked for anyone?
Click to expand...
Click to collapse
Yeah worked for me. Stock, unlocked, unrooted 16gb WiFi.
#1 reason to always unlock an android. Lol, sorry man. I seriously wonder why that kind of thing happens, I don't trust OTA and besides, I never use stock recovery so I just flash
Sent from my Nexus 9 using XDA Free mobile app
adstro said:
Has the 5.0.2 OTA worked for anyone?
Click to expand...
Click to collapse
Yes, stock unrooted but unlocked.
You can download a copy of factory image. When you unzip it throw all the files into your platform-tools folder. Then just run the batch file Flash-all. Needs access to fastboot and adb but will repair boot sequence.
This is what happen been messing with it going back and forth between Jasmine and stock. Well I flashed the stock .tar with odin and then it won't read my sim card anymore and I can't get flashfire to work. The phone status shows custom no matter what I do. Have odin the OB6 and OF1 stock shows an unlocked lock saying custom on boot screen..I did triangle away and that went away for a little bit then came back after a few restarts. And when I root it fails, when I did have the root I'm the stock it wouldn't let me flash. I'm kinda lost now, anyone have any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry, but if you can't flash any official firmware with odin looks like a motherboard problem to me.
---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------
Did you try to go to recovery and wipe cache partition then wipe data/factory reset ?
thunderblaster88 said:
This is what happen been messing with it going back and forth between Jasmine and stock. Well I flashed the stock .tar with odin and then it won't read my sim card anymore and I can't get flashfire to work. The phone status shows custom no matter what I do. Have odin the OB6 and OF1 stock shows an unlocked lock saying custom on boot screen..I did triangle away and that went away for a little bit then came back after a few restarts. And when I root it fails, when I did have the root I'm the stock it wouldn't let me flash. I'm kinda lost now, anyone have any ideas?
Click to expand...
Click to collapse
I flash the jasmine rom but some mudule exposed stop working and i got back to 4.4.4 but my note have the same boot image
aaroon200 said:
Sorry, but if you can't flash any official firmware with odin looks like a motherboard problem to me.
---------- Post added at 11:55 PM ---------- Previous post was at 11:50 PM ----------
Did you try to go to recovery and wipe cache partition then wipe data/factory reset ?
Click to expand...
Click to collapse
I can flash the official firmware..that's what it's on with it saying it's custom. That's why I'm not understanding. I did wipe those.
Sent from my VS985 4G using Tapatalk
'Cause you still have a modified firmware, that's why
Sent from my SM-N900V using Tapatalk
aaroon200 said:
'Cause you still have a modified firmware, that's why
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I flashed on Odin the stock one, should t that revert the firmware? If not what do I do?
Sent from my VS985 4G using Tapatalk
I take it this is also causing my sim card problem as well. It does not say insert sim card or anything, only when I go to the mobile data toggle it says to insert one.
Sent from my VS985 4G using Tapatalk
Stock 1?
You should flash the original firmware from keis or from this page :
http://www.sammobile.com/firmwares/database/SM-N900V/
and start all over again, that should fix your problems.
Sent from my SM-N900V using Tapatalk
aaroon200 said:
Stock 1?
You should flash the original firmware from keis or from this page :
http://www.sammobile.com/firmwares/database/SM-N900V/
and start all over again, that should fix your problems.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
That's what I flashed, well I got it from Google drive that someone else uploaded so it wasnt a few hour download. The one I have worked the first 3 times. I'll give this one a download and try because why not
Btw I wanted to say thank you for helping me out with this. I've been rooting and all this since my eris so I know how it goes and This stuff happens. It's not the first time I've had a problem similar to this. I've tried everything I could think of like 5 times today for the last 8 hours or so tho
Sent from my VS985 4G using Tapatalk
thunderblaster88 said:
That's what I flashed, well I got it from Google drive that someone else uploaded so it wasnt a few hour download. The one I have worked the first 3 times. I'll give this one a download and try because why not
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Sometimes files get corrupted try the original. It takes about 2 hours to download [emoji1]
Sent from my SM-N900V using Tapatalk
aaroon200 said:
Sometimes files get corrupted try the original. It takes about 2 hours to download [emoji1]
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I just edited this post of you didn't see lol yeah I know it happens that's why i figured I might as well just download it anyway. Yeah freaking 2 hours is just crazy..see what happens and I'll let you know
Sent from my VS985 4G using Tapatalk
You can always paid the $7 dollars for one week of premium Speed.
[emoji12]
Sent from my SM-N900V using Tapatalk
Now I'm waiting for the download and playing on it and got this too lol
Snapchat is blocking rooted phones again. Lol
Restart it. Your gonna delete all that shiet anyways.
Sent from my SM-N900V using Tapatalk
thunderblaster88 said:
Now I'm waiting for the download and playing on it and got this too lol
Click to expand...
Click to collapse
I believe that's from verizon or Knox when using the root method of 1.tar and 2.tar, try this one instead : http://forum.xda-developers.com/verizon-galaxy-note-3/general/ob6-of1-n900v-note-3-verizon-oneclick-t3333569 after you back to original stock, this is the best method so far, and you will not get any strange warnings.
Ya it is, Knox
Sent from my SM-N900V using Tapatalk
aaroon200 said:
I believe that's from verizon or Knox when using the root method of 1.tar and 2.tar, try this one instead : http://forum.xda-developers.com/ver...b6-of1-n900v-note-3-verizon-oneclick-t3333569 after you back to original stock, this is the best method so far, and you will not get any strange warnings.
Click to expand...
Click to collapse
This or the one I used. I never did the 1.tar 2.tar one I used the latest one click. Also I did the firmware from sammobile and same thing. So he said Knox then what do I do or are my options?
Sent from my VS985 4G using Tapatalk
thunderblaster88 said:
This or the one I used. I never did the 1.tar 2.tar one I used the latest one click. Also I did the firmware from sammobile and same thing. So he said Knox then what do I do or are my options?
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Ok, you already flash the firmware?
any screenshots ?
aaroon200 said:
Ok, you already flash the firmware?
any screenshots ?
Click to expand...
Click to collapse
Yeah I did and it's still says custom..wouldn't let me root. Thing is is that pop up was Knox and said to reset I think that would set it back, cause before I flashed the firmware from SM I did a factory wipe then I'm download mode it said official..but after I flashed the firmware it says custom again lol. I'm gknna. I'm setting the phone back up now and waiting to see if that pops up again. My sim card hasn't been in the phone pretty much all day. Been in my g3. since the note won't read it as of now and yes I've tried putting pressure on the sun cause I know they had problems my other 2 old note 3's had that problem. This happen last Night when I was messing around before bed that's why I didn't mess with it too today.. Sorry and thank you guys for the help again
Sent from my VS985 4G using Tapatalk
thunderblaster88 said:
Yeah I did and it's still says custom..wouldn't let me root. Thing is is that pop up was Knox and said to reset I think that would set it back, cause before I flashed the firmware from SM I did a factory wipe then I'm download mode it said official..but after I flashed the firmware it says custom again lol. I'm gknna. I'm setting the phone back up now and waiting to see if that pops up again. My sim card hasn't been in the phone pretty much all day. Been in my g3. since the note won't read it as of now and yes I've tried putting pressure on the sun cause I know they had problems my other 2 old note 3's had that problem. This happen last Night when I was messing around before bed that's why I didn't mess with it too today.. Sorry and thank you guys for the help again
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Don't do anything yet after flashing , you still have your old data on the phone, now go to recovery and do some wipes, wipe cache partition and wipe data/factory reset and that should fixed.
---------- Post added at 04:32 AM ---------- Previous post was at 04:21 AM ----------