Hello, I am uploading my MOD ROM and kernel for Sprint. A previous attempt failed, and I just learned that the boot.img I had received was not the actual stock Sprint ROM, so the RAMdisk did not work.
Need someone, or some people to test, so I can make an official post in the ROM section.
As always, I recommend doing a full backup in TWRP to be able to restore to if the ROM does not work.
Also, Titanium Backup is the go-to app to backup your apps (do not backup system apps, only apps that you yourself have downloaded).
Must be on the latest TWRP. Must be fully decrypted. Do a clean flash.
Here is the latest test. I believe it should be fine. Static boot will remain since you have a bootloader not made for your device.
(reuploading, old zip would not flash due to a typo)
Updated, fixed link : https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
Tilde88 said:
As always, I recommend doing a full backup in TWRP to be able to restore to if the ROM does not work.
Also, Titanium Backup is the go-to app to backup your apps (do not backup system apps, only apps that you yourself have downloaded).
Must be on the latest TWRP. Must be fully decrypted. Do a clean flash.
Here is the latest test. I believe it should be fine. Static boot will remain since you have a bootloader not made for your device.
https://mega.nz/#!bUlE1RRa!Owuf3BVtZ...Gq8iNcSBRbe4bw
Click to expand...
Click to collapse
what is the decryption key? it will not allow me to download it without it.
ruthlessnature said:
what is the decryption key? it will not allow me to download it without it.
Click to expand...
Click to collapse
whoops
Tilde88 said:
whoops
https://mega.nz/#!bUlE1RRa!Owuf3BVtZ3Hlm96b5jVPGDZZP7gsMGq8iNcSBRbe4bw
Click to expand...
Click to collapse
thanks gonna download now and give it a go I will report back as soon as I can.
ruthlessnature said:
thanks gonna download now and give it a go I will report back as soon as I can.
Click to expand...
Click to collapse
hold on. i gotta reupload... there was a typo in the script >.> my bad
Tilde88 said:
hold on. i gotta reupload... there was a typo in the script >.> my bad
Click to expand...
Click to collapse
Ok let me know when it's good to go.
Sent from my iPhone using Tapatalk
ruthlessnature said:
Ok let me know when it's good to go.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Here is the updated link
Sorry about that!
https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
Tilde88 said:
Here is the updated link
Sorry about that!
https://mega.nz/#!LdkglIyY!8xJVm_1tTNwfrItn-t1n9bq4ZPginAL-DpW07hMwj8o
Click to expand...
Click to collapse
I have not been able to get it to boot up. it stays stuck on the static screen? I tried 3 times and did a full wipe all 3 times.
ruthlessnature said:
I have not been able to get it to boot up. it stays stuck on the static screen? I tried 3 times and did a full wipe all 3 times.
Click to expand...
Click to collapse
How long are you waiting? First boot takes about 15 mins.
You still have to do whatever the static boot fix is.
Tilde88 said:
How long are you waiting? First boot takes about 15 mins.
You still have to do whatever the static boot fix is.
Click to expand...
Click to collapse
I waited awhile id say atleast 30 min each time. it never gets to the point where I can shut off the screen to do the static fix. I'm in the process of trying again I will let it sit for awhile longer and see what happens.
Still couldnt get it to boot not sure why.
I locked up too. It happens just about a second into the boot animation. I can see maybe colored balls swirling and then some light text starts to fade in right in the center of the screen then it locks up. Pulled the battery and booted it up a 2nd time just in case but it also locked up and never finished. Gave it 30 minutes the first time and 15 on the second boot attempt.
Related
Well I liked how the xoom was running at 1500 so much that I changed the SetCPU settings to 'start at boot.'
I restarted it for another reason with QuickStart. I get the 'Dual Core' screen, then it just loops the 'exploding honeycomb' over and over and over and over.
Did I ruin the xoom? Anyway for me to fix this with ADB? Any way to turn the device off?
I can hard-reset by pressing Up Volume and the On button. But that just restarts it and the problem is the same.
I have a bad feeling I'm just frying the damn thing right now.
Please give me advice somebody.
Later.
You did not say which xoom you have. If you can get into recovery, you can power it down. In recovery you can factory reset also. There is a txt file you can create on your sdcard to tell setcpu to stop, but i don't have a link to the file or whats suppose to be in it.
Sorry I have wifi xoom.
Omg I just rebooted into recovery using adb reboot recovery.
EDIT: Now I'm at Android with Triangle with exclamation point in it.
Now what?
Well I managed to write the boot.img back to the Xoom but it still didn't work.
I shouldn't have messed with SetCPU!
Think costco will still take it back? Lol.
Don't think I won't try.
Sprockethead said:
Well I managed to write the boot.img back to the Xoom but it still didn't work.
I shouldn't have messed with SetCPU!
Think costco will still take it back? Lol.
Don't think I won't try.
Click to expand...
Click to collapse
Yes costco will take it back aslong as its been 90 days or less. You don't have CWM then. Go here http://forum.xda-developers.com/showthread.php?t=1049485 Download clockworkmod and follow the instructions. Then factory reset in clockworkmod.
I just don't understand why flashing the stock boot image doesn't fix it. Doesn't that overwrite all my apps and stuff?
Sprockethead said:
I just don't understand why flashing the stock boot image doesn't fix it. Doesn't that overwrite all my apps and stuff?
Click to expand...
Click to collapse
No the boot.img has nothing to do with apps. System.img is the system apps and other stuff. Data.img is where setcpu is.
Sent from my PC36100
bwcorvus said:
No the boot.img has nothing to do with apps. System.img is the system apps and other stuff. Data.img is where setcpu is.
Sent from my PC36100
Click to expand...
Click to collapse
Thanks so much. I flashed the stock system.img and it took away my root. Setcpu couldn't get root access when restarted and so it booted up normally. All my settings and widgets and everything were still there, too!
Thanks so much. I'm sure you all know how frustrating it can be. You saved me from a pseudo-bricked xoom.
Having said that, I wish I didn't feel the need to overclock this machine. It's so awesome as-is, but I guess I'm just greedy!
Oh well. Problem resolved. Thanks again. Later.
i did the 1 click all and now im stuck at the nexus logo...does it take a really long time to reboot after you go through everything? i think everything went fine though.
hegemytouch said:
i did the 1 click all and now im stuck at the nexus logo...does it take a really long time to reboot after you go through everything? i think everything went fine though.
Click to expand...
Click to collapse
If you're stuck at Nexus logo, you're in no way bricked. Worst case is your ROM can't boot, which is easily fixable. Boot to fastboot mode (Power button+vol down), and via your toolkit you can factory reset a new stock rom. Or possibly flash another pre-rooted rom. As long as you can get to fastboot mode, you're all good.
thanks so much man...how long does the initial boot take after rooting installing cwm busy box and all? i did the 1 click all...
hegemytouch said:
thanks so much man...how long does the initial boot take after rooting installing cwm busy box and all? i did the 1 click all...
Click to expand...
Click to collapse
Honestly, I don't know. Sometimes initial boot can take up to 5 minutes, but if it's longer than that, changes are something is not working. You could try going to recovery and factory reset and clear caches once more, and reboot again. Else I would try re-flashing stock rom. I haven't tried 1-click all method, I did it one single step at a time...
wow dude clearing cache and a factory reset worked...i love you lol
is it ok to now install a custom rom?
hegemytouch said:
is it ok to now install a custom rom?
Click to expand...
Click to collapse
Flash all you want
Make a complete nandroid backup first, so you can always revert back to a working rom, just in case.
As long as you stick with flashing N4 roms on the N4 (!!) and follow instructions, you should be good.
Hi guys, I flashed a jamal's 4.3 rom coming from omega's google edition rom and i did the usual stuff like I always have factory reset etc.. and i reboot the system and fix permissions as usual and my phone is now stuck on the omega's spinning boot up animation with the phone vibrating.
HELP!!!
Re-download the rom, could be a bad download. Did you check the md5sum?
jd1639 said:
Re-download the rom, could be a bad download. Did you check the md5sum?
Click to expand...
Click to collapse
what's a md5sum? :L i can't since my phone doesn't show up on my computer
sbouzyk said:
what's a md5sum? :L i can't since my phone doesn't show up on my computer
Click to expand...
Click to collapse
It's a long alpha-numeric number that is associated with the file. Next time you download a rom look for it on the download page. When you down load a file the md5sum should match the original indicating a good download. There are apps that check the md5 and most file managers will show it in properties
ok, but how do i get out of the bootloop
sbouzyk said:
ok, but how do i get out of the bootloop
Click to expand...
Click to collapse
If you've done the factory reset and that doesn't get you out I'm guessing the rom you flashed was a bad download. You made a nandroid backup before you flashed the rom, right. Boot back into recovery and restore it. Then re download the rom and try it again
jd1639 said:
If you've done the factory reset and that doesn't get you out I'm guessing the rom you flashed was a bad download. You made a nandroid backup before you flashed the rom, right. Boot back into recovery and restore it. Then re download the rom and try it again
Click to expand...
Click to collapse
i didn't make a nandroid backup...
sbouzyk said:
i didn't make a nandroid backup...
Click to expand...
Click to collapse
Live and learn, I was afraid of that. You're probably going to have to use Odin then which will return you back to stock. And then start everything over again. Have you let the boot loop go for like 5 minutes. Sometimes it can take that long on first boot, but the vibration isn't normal.
jd1639 said:
Live and learn, I was afraid of that. You're probably going to have to use Odin then which will return you back to stock. And then start everything over again. Have you let the boot loop go for like 5 minutes. Sometimes it can take that long on first boot, but the vibration isn't normal.
Click to expand...
Click to collapse
the thing is though, i have flash this download of the rom before, and it was fine. i just got bored of it and downloaded another rom. i then decided to go back to the rom again.
sbouzyk said:
the thing is though, i have flash this download of the rom before, and it was fine. i just got bored of it and downloaded another rom. i then decided to go back to the rom again.
Click to expand...
Click to collapse
Try flashing it again then. Do all the wipes first then flash it and then flash gapps. Did you flash the gapps package? I'm not sure what rom you're trying to flash but it probably requires gapps too.
jd1639 said:
Try flashing it again then. Do all the wipes first then flash it and then flash gapps. Did you flash the gapps package? I'm not sure what rom you're trying to flash but it probably requires gapps too.
Click to expand...
Click to collapse
gapps isn't on my phone so i cant flash it. i've flash it about ten times now and it won't work. it must be a bad download even though i flashed it before. after i flash the rom, it shows the boot animation of the rom i had been using before. werid huh? the only option i have now is to buy a micro sd card and put the rom on that and flash it that way. i really don't want to use odin.
sbouzyk said:
gapps isn't on my phone so i cant flash it. i've flash it about ten times now and it won't work. it must be a bad download even though i flashed it before. after i flash the rom, it shows the boot animation of the rom i had been using before. werid huh? the only option i have now is to buy a micro sd card and put the rom on that and flash it that way. i really don't want to use odin.
Click to expand...
Click to collapse
The sd card is a good idea. You're going to want one anyway.
jd1639 said:
The sd card is a good idea. You're going to want one anyway.
Click to expand...
Click to collapse
thanks for all your help mate. guess I'm going to be a LOT more careful in the future. now im phoneless anyway cheers for the help
sbouzyk said:
thanks for all your help mate. guess I'm going to be a LOT more careful in the future. now im phoneless anyway cheers for the help
Click to expand...
Click to collapse
Np
sbouzyk said:
thanks for all your help mate. guess I'm going to be a LOT more careful in the future. now im phoneless anyway cheers for the help
Click to expand...
Click to collapse
You're just going to give up? Seriously? It's really easy to flash stock fw with Odin. And also easy to root afterwards, to each their own.
norml said:
You're just going to give up? Seriously? It's really easy to flash stock fw with Odin. And also easy to root afterwards, to each their own.
Click to expand...
Click to collapse
What do you mean giving up? I'm going to wait until my microSD card comes and then I will transfer the zip file that way. I don't have time to fiddle with odin. Besides I don't even have a pc, i have bootcamp, which takes a year to boot.
Every once in a while, when I reboot my phone, it'll hang at the Axon logo (after the little "swoosh") for 15-20 minutes before it will completely boot up? It isn't running through the "Android is starting apps", I know to expect that when I clear the cashe or install a fresh ROM. This is just on a "Hey, I'm going to reboot my phone today".
I am rooted (for custom fonts and emoji's), no Xposed.
It doesn't happen every time, maybe 3 times over the past month.... But it always happens at the worst time (it seems).
My external SD card has about 28gb of stuff on it, could it be scanning that?
Do you use SuperSU ?
XblackdemonX said:
Do you use SuperSU ?
Click to expand...
Click to collapse
Yes
2.76
tele_jas said:
Yes
2.76
Click to expand...
Click to collapse
Using 2.76 su with Xposed, no long booting time,
Started happening when you replace fonts and emojis?
DrakenFX said:
Using 2.76 su with Xposed, no long booting time,
Started happening when you replace fonts and emojis?
Click to expand...
Click to collapse
No, that's why it's so hard to narrow down.... First time it did it, I actually had Xposed installed. I restored my TWPR backup to when I didn't flash any extra's, just the stock apps and my user apps. I let that be for a few days and it did it to me then too, so I realized my fonts and emoji's didn't make a difference, so I put them back in, but left Xposed off.
I wish I had a backup of before I installed all my apps, right after I installed TWRP, but I deleted it on accident.
tele_jas said:
Yes
2.76
Click to expand...
Click to collapse
I suspect that this could be why. Try SuperSU 2.65 like suggested in DrakenFX's post
Source: My OnePlus One takes 7 minutes to boot
Maybe you can get a logcat while it boots? We might be able to see what's happening in those 15 minutes.
dennis96411 said:
Maybe you can get a logcat while it boots? We might be able to see what's happening in those 15 minutes.
Click to expand...
Click to collapse
that is actually a good solution ,
Root just disappeared.
This is not a huge problem but when I go to TWRP to reinstall SuperSU, I can't get to the files so I can't install SuperSU.
I have now a MegaPixel ROM with EX kernel and I want to go back to stock. With no root, kernel and recovery... Just don't know how to.
Step by step here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page567
HeroPlane said:
Root just disappeared.
This is not a huge problem but when I go to TWRP to reinstall SuperSU, I can't get to the files so I can't install SuperSU.
I have now a MegaPixel ROM with EX kernel and I want to go back to stock. With no root, kernel and recovery... Just don't know how to.
Click to expand...
Click to collapse
Follow the guidelines on this page and download the factory image from Google server to return 100% stock.
https://developers.google.com/android/images
RoyJ said:
Step by step here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page567
Click to expand...
Click to collapse
therock3181 said:
Follow the guidelines on this page and download the factory image from Google server to return 100% stock.
https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried to reinstall SuperSU but now its stuck on boot animation. How can I fix this?
I don't think you can do a factory reset if you are on a custom Rom. Power down your phone by holding down the power button until the phone shuts down. Go into bootloader mode by pressing power and volume down buttons at the same time. Flash complete factory image from Google site using flash-all.bat command. If you don't know how to do that follow the XDA/Heisenberg guide only to the point where it shows you how to flash. Do not flash all the pieces individually like in the guide. Just use flash-all.bat command like Google suggests.
HeroPlane said:
I tried to reinstall SuperSU but now its stuck on boot animation. How can I fix this?
Click to expand...
Click to collapse
Use the link I posted above. Read it and follow the return to stock section. Like I mentioned earlier, that's a step by step guide to all things 6P. How to root, how to return to stock and everything in between. It has (or at least links you to) all the tools you need. It's a lot more thorough than I am, quite frankly. Just do your best to follow the return to stock section of the guide and if you run into any issues quote me again and let me know where you're stuck and I'll see if I can help. But you're asking for a step by step on how to recover and I've already provided you with a link with those exact steps. Good luck. Specifically steps 10 or 11 depending on if you want to keep your data intact.
RoyJ said:
Use the link I posted above. Read it and follow the return to stock section. Like I mentioned earlier, that's a step by step guide to all things 6P. How to root, how to return to stock and everything in between. It has (or at least links you to) all the tools you need. It's a lot more thorough than I am, quite frankly. Just do your best to follow the return to stock section of the guide and if you run into any issues quote me again and let me know where you're stuck and I'll see if I can help. But you're asking for a step by step on how to recover and I've already provided you with a link with those exact steps. Good luck. Specifically steps 10 or 11 depending on if you want to keep your data intact.
Click to expand...
Click to collapse
I flashed back to stock like the guide told me. Now its bootlooping with the normal Nexus animation. It means that now I have stock ROM but still bootloop...
HeroPlane said:
I flashed back to stock like the guide told me. Now its bootlooping with the normal Nexus animation. It means that now I have stock ROM but still bootloop...
Click to expand...
Click to collapse
What were the exact steps you took? Also, how long has it been boot looping? First boot on a factory image flash can take a while. I've waited like 10 full minutes before boot.
RoyJ said:
What were the exact steps you took? Also, how long has it been boot looping? First boot on a factory image flash can take a while. I've waited like 10 full minutes before boot.
Click to expand...
Click to collapse
I did all the steps in part 10 with angler 7.1.2
It was bootlooping for 5 minute or so. I turned the phone off (While it was bootlooping) and now when I try to boot I get a "No Command" with a opened Android screen. What should I do now?
Maybe I can still flash TWRP and do stuff there?
HeroPlane said:
I did all the steps in part 10 with angler 7.1.2
It was bootlooping for 5 minute or so. I turned the phone off (While it was bootlooping) and now when I try to boot I get a "No Command" with a opened Android screen. What should I do now?
Maybe I can still flash TWRP and do stuff there?
Click to expand...
Click to collapse
The no command screen with an Android on its back is stock recovery. When you see that, hold volume up and while holding volume up, press the power button. That'll get you inside stock recovery. From there you can factory reset. This will likely wipe your internal storage. I'm not exactly sure on that, but assume it does. If that's not an issue, do it and try booting again, but wait longer this time. Leave in on the charger and wait 10 minutes or so. If it still won't boot, try again with 7.1.1 factory images. Also if you're using the flash all .bat file try manually flashing each partition using fastboot.
Edit: If you didn't already, don't lock the bootloader. You won't be able to use fastboot or flash TWRP (if that's what you want to do) with it locked.
RoyJ said:
The no command screen with an Android on its back is stock recovery. When you see that, hold volume up and while holding volume up, press the power button. That'll get you inside stock recovery. From there you can factory reset. This will likely wipe your internal storage. I'm not exactly sure on that, but assume it does. If that's not an issue, do it and try booting again, but wait longer this time. Leave in on the charger and wait 10 minutes or so. If it still won't boot, try again with 7.1.1 factory images. Also if you're using the flash all .bat file try manually flashing each partition using fastboot.
Edit: If you didn't already, don't lock the bootloader. You won't be able to use fastboot or flash TWRP (if that's what you want to do) with it locked.
Click to expand...
Click to collapse
Can't get to the recovery. Forgot to mention that the "No command" screen is flashing. Like, I can see it for less that a second, it turns black, and comes back again for less than a second. Is it looping too?
double
HeroPlane said:
Can't get to the recovery. Forgot to mention that the "No command" screen is flashing. Like, I can see it for less that a second, it turns black, and comes back again for less than a second. Is it looping too?
Click to expand...
Click to collapse
Sounds like it. That's not good, it sounds​ like a real issue here. How did this end up happening in the first place? You factory reset from TWRP and all this happened? That should have not made you boot loop. You should have been fine and booted and had to sign in again, etc.
Did you lock the bootloader?
RoyJ said:
Sounds like it. That's not good, it sounds​ like a real issue here. How did this end up happening in the first place? You factory reset from TWRP and all this happened? That should have not made you boot loop. You should have been fine and booted and had to sign in again, etc.
Did you lock the bootloader?
Click to expand...
Click to collapse
Didn't lock bootloader
I did the factory reset from system.
I hope it's not a big issue cause I just paid 150$ to fix the screen. I just wanted to give it to my mom fresh (with no root, custom ROM etc...)
HeroPlane said:
Didn't lock bootloader
I did the factory reset from system.
I hope it's not a big issue cause I just paid 150$ to fix the screen. I just wanted to give it to my mom fresh (with no root, custom ROM etc...)
Click to expand...
Click to collapse
Yeah if you're not on stock, don't factory reset from the system. Use TWRP. Try to fastboot flash TWRP back on the phone and see if you can boot to that.
RoyJ said:
Yeah if you're not on stock, don't factory reset from the system. Use TWRP. Try to fastboot flash TWRP back on the phone and see if you can boot to that.
Click to expand...
Click to collapse
TWRP works! OK that's a good sign (I think so...)
I wiped EVERYTHING (Dalvik/ART cache, cache, system, Data and internal storage)
I will probably try to flash stock now.
HeroPlane said:
TWRP works! OK that's a good sign (I think so...)
I wiped EVERYTHING (Dalvik/ART cache, cache, system, Data and internal storage)
I will probably try to flash stock now.
Click to expand...
Click to collapse
Flash stock minus recovery, leave TWRP. See if you can get it to boot. Try 7.1.1 if possible this time, though.
RoyJ said:
Flash stock minus recovery, leave TWRP. See if you can get it to boot. Try 7.1.1 if possible this time, though.
Click to expand...
Click to collapse
I think I know why 7.1.2 didn't boot
I have a EX kernel updated to march security. I should download a stock with march security or lower.
RoyJ said:
Flash stock minus recovery, leave TWRP. See if you can get it to boot. Try 7.1.1 if possible this time, though.
Click to expand...
Click to collapse
Wow man, thank you so much!
The phone is working after I flashed 7.1.1 march
You are the best!!! :victory:
HeroPlane said:
Wow man, thank you so much!
The phone is working after I flashed 7.1.1 march
You are the best!!! :victory:
Click to expand...
Click to collapse
Glad you got it sorted out!