Related
Hey guys..
Straight forward question..
Is it possible to password protect our Download and Recovery modes?
And i mean when you press and hold vol dwn+home+power method. Not through the android software reboot menu.
I want/like this idea because if someone were to steal my phone. They would NEVER be able to flash a custom ROM or even flash a stock ROM img. They would be completely locked out making the device useless to them.
The only way i think they could get past it is by using JTAG to overwrite the download partition with a stock one. But hardly anyone has a JTAG device.
Well this would be awesome. lol
Have at it
Im guessing it would require a modified bootloader. Not really sure though. Ive wondered about this myself. Never seen it done though.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Im guessing it would require a modified bootloader. Not really sure though. Ive wondered about this myself. Never seen it done though.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I think it would be the ultimate level of security. And i agree a modified bootloader would be necessary. How one would go abouts creating one i am clueless.
elesbb said:
I think it would be the ultimate level of security. And i agree a modified bootloader would be necessary. How one would go abouts creating one i am clueless.
Click to expand...
Click to collapse
As am I lol! This ones a bit above my skill level!
Problem is, itd have to be redone for each model. Unless there was a way to have sonething that could sit on top of or intercept power on and run before the bootloader....I really have no idea though, just tossing ideas!
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
As am I lol! This ones a bit above my skill level!
Problem is, itd have to be redone for each model. Unless there was a way to have sonething that could sit on top of or intercept power on and run before the bootloader....I really have no idea though, just tossing ideas!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Too bad it's not the HD2
But yes I think one would need to be made for each device... and if I or anyone can create the bootloader, how would you flash the bootloader? JTAG device?
Sent from my SGH-T999 using Tapatalk 2
Believe it or not, Im pretty sure you can flash any partition through Odin, so there you go! I could be wrong of course....
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Believe it or not, Im pretty sure you can flash any partition through Odin, so there you go! I could be wrong of course....
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Hey you could be right too! I never knew that! Hmmm I think in my spare time I shall delve into this!
Sent from my SGH-T999 using Tapatalk 2
Best of luck on it man! If I can be of help let me know, though on this dont expect a lot from me!!
Sent from my SGH-T999 using xda app-developers app
that is a great idea indeed.:good:
Very interesting topic, but I think it is impossible to do (Recovery & download) are design to prevent forgotten password issues.
What a pity
Guys i thnk if it can be done
It will be easy to install it on our devices if rooted (stock android)
As companies like sammy ,htc have diff kernals
I thnk we can successfully do this fr nexus ,micromax ,karbonn etc.....
Lets have a try
Ny one tried this before
If so plz gimme a guide of it so that it will b easy fr me
Lemmi try my best fr us to have ultimate theft protection on our android devices
I hope if it wrks google may add it on its future devices
The "ultimative" protection would be:
When a phone is stolen, you can remotely trigger "the suicide button" xD
When it is triggered and the phone receives the command (Even if the phone is running other ROM) it reboots the phone and erases the Bootloader and some other things that are important for the phone to work.
Best. Protection. Ever.
Second thing I could imagine is that phone companies could protect the download mode with a password (12 digits or so).
That password will come printed on one of the manuals when you buy the phone.
If you attempt to flash an image in download mode, you will be prompted for the password.
And, optionally, if you put the password 10 times wrong, it will erase bootloader and etc.
Third idea: The download mode only will prompt for a password (printed on the manual), if you atempt to flash another ROM on it... Because this will change the confidential signature that the old ROM has passed to the download mode.
(I am not sure if this could be done. I'm just saying ideas...)
OK so I rooted all my previous phones with no issues, just wondering running stock this phone is pretty fast don't know how much "faster" it can get. I know all the features rooting can bring like removing annoying bloatware, carrier iq, build props etcc. What else could you do with these roms? With stock I already could do a lot of the stuff I couldn't do with previous phones running stock. I know overclocking, undervolting anything else I missed that these roms provide apart from asthetic looks?
I guess I just wanted the opinion from people rooted to see if you get that "night & day" difference effect that you get when you root
Sent from my SGH-T999 using xda app-developers app
If it wasn't for removing bloat and carrierIQ i would be satisfied with stock. BUT AOSP/AOKP is my main reason and 4.2. The TouchJizz ROMs aren't my thing overall. But i think stock out of the box is great, i have plenty of friends with the S3 that wont let me tough their phone cause they are so happy with it stock.
Sent from my SGH-T999 using xda premium
There are way too many junkwares phone provider put on the stock TW. Even pure TW contains Samsung's junkwares. Rooting will allow you to remove or freeze those junkwares which makes the phone performs even better with better batt life. You can also install a firewall such as DroidWall to block internet access from apps. Block ads with AdAway. Block apps from autorun themselves when certain event occurs such as power is plugged in. There are endless helpful things you can do with a rooted phone.
I'd suggest reading more about rooting, flashing, custom recovery and see what you're missing without root.
S-beamed from my GSIII via xda premium
Yes rooting is really worth it.
People that I work with have note 2 and s3 and my s3 is much faster and snappier then all of theirs.
Sent from my SGH-T999 using xda premium
mt3g said:
If it wasn't for removing bloat and carrierIQ i would be satisfied with stock. BUT AOSP/AOKP is my main reason and 4.2. The TouchJizz ROMs aren't my thing overall. But i think stock out of the box is great, i have plenty of friends with the S3 that wont let me tough their phone cause they are so happy with it stock.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yeah this is one of the few phones that don't come messed up from the box, I would say battery life could definitely improve on jb so I know rooting will help that a bit. Thanks for input
Sent from my SGH-T999 using xda app-developers app
[email protected] said:
There are way too many junkwares phone provider put on the stock TW. Even pure TW contains Samsung's junkwares. Rooting will allow you to remove or freeze those junkwares which makes the phone performs even better with better batt life. You can also install a firewall such as DroidWall to block internet access from apps. Block ads with AdAway. Block apps from autorun themselves when certain event occurs such as power is plugged in. There are endless helpful things you can do with a rooted phone.
I'd suggest reading more about rooting, flashing, custom recovery and see what you're missing without root.
S-beamed from my GSIII via xda premium
Click to expand...
Click to collapse
Yeah all those things you stated I already knew, I like the adaway stuff several other apps that can do that too. Also voodoo sound is nice. Voltage control all that.. I'm pretty careful and all but I guess I just don't want to deal with all the hassle. Backing up nv, roms, apps whole nine yards.
Sent from my SGH-T999 using xda app-developers app
My question is i read around forums people stating that triangle away can't take away the tripping counter when you flash a s3 that came with JB already installed out the box any truth?
Just would like to know since I have a long warranty on it just in case.
Also backing up your emei would insure you will get it back if something goes wrong? Because I saw in that forum it was a mixed bag some people could get it others couldn't and had their 4G missing too
Sent from my SGH-T999 using xda app-developers app
Yes............
Rooting IS worth it, next QUESTION!
Lol
And they have a thread on how to not trip the counter.
And as far as stock jb tripping the counter... haven't heard that but I honestly dont think it will unless you flash a new rom
Sent from my SGH-T999 using xda premium
Counter thing is dumb in my opinion. I'm sure there is a work around, Odin back to ICS and then Odin JB then go from there maybe, idk.
Yes, banking up your imei is a full proof plan and use twrp instead of cwm!
Sent from my SGH-T999 using xda premium
Oh okay one more thing backing up. Where you guys backup your roms internal or sd card Which one is more ideal? Just wondering since I never had phone with this much storage. I assume in touch recovery it let's you decide when you're backing up right?
Sent from my SGH-T999 using xda app-developers app
Ideal should be in sd card.
NOTE* always make a backup before you flash anything, I cant stress that enough because it will save your life*
Also do not mess with it while its in your card because it will not boot up. My suggestion is leave it as is
To be honest though either or, it would not be a problem... me, I have it in my ad card
Sent from my SGH-T999 using xda premium
The_F_Word said:
Ideal should be in sd card.
NOTE* always make a backup before you flash anything, I cant stress that enough because it will save your life*
To be honest though either or, it would not be a problem... me, I have it in my ad card
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Especially a backup of your imei... Can't stress that enough.. I learned that hard way and I thought my phone was completely screwed so i got two new gs3's not knowing it was such an easy fix even if you didn't back it up
Sent from my SGH–T999 using xda premium running on Jelly Bean 4.2.1
The_F_Word said:
Ideal should be in sd card.
NOTE* always make a backup before you flash anything, I cant stress that enough because it will save your life*
Also do not mess with it while its in your card because it will not boot up. My suggestion is leave it as is
To be honest though either or, it would not be a problem... me, I have it in my ad card
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks dude appreciated
Sent from my SGH-T999 using xda app-developers app
Rooting is definitely worth it. Probably the best things you can do with it is remove bloatware, install an Ad-Blocker, and control the CPU to increase battery life or performance. With the Triangle Away app, you can easily reset the Custom Binary counter for warranty exchanges as I have done a few times.
mt3g said:
Counter thing is dumb in my opinion. I'm sure there is a work around, Odin back to ICS and then Odin JB then go from there maybe, idk.
Yes, banking up your imei is a full proof plan and use twrp instead of cwm!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
The is an app called triangle away that resets the counter. If you don't know, don't offer useless advice.
Backing up your NV data is a "fool" not "full" proof plan indeed tho.
daxecutioner24 said:
Oh okay one more thing backing up. Where you guys backup your roms internal or sd card Which one is more ideal? Just wondering since I never had phone with this much storage. I assume in touch recovery it let's you decide when you're backing up right?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
When in recovery you can choose where to back up to. I would personally read thru the stickied threads and get some information that has been deemed infallible by the higher ups. Asking basic stuff on a thread sometimes leads idiots to respond like they know something. The info on the stickies is concrete and not opinion based or anything.
Rooted my i317 2 days ago with the "no triangle counter" method. All was good, got TWRP installed, nandroided stock and did my thing. Been rooting phones for many years and have yet to brick anything *knocks on virtual wood*. Installed paranoid android, and all was awesome. Decided to give another rom a try... Cant remember which, but im not thinking thats the issue.
Wiped, flashed, no errors, rom booted normally, but as i unlock the device i get three force close errors. Then reboot. Over and over. Restored three different backups and all three do the same thing. Never run into this one before. Admittedly i am worried. Not a rich man and bought this phone outright...
I am hoping flashing in odin the original root tar file will correct the issue. But honestly wanted to do some reading and post this first. Any help would be greatly appreciated.
Sent from my SAMSUNG-SGH-I957 using Tapatalk
Did you try flashing a touch wiz kernel before going back to a nandroid? If not try that and if so try a factory reset and then a good old reboot!
I assume you tried a cm10.1 rom?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Same thing happened to me and I did just use odin to push that tar file through, rerooted, and flashed in my rom. That to me seems to be the fix for the bootloop imo. But someone with more knowledge could correct me if im wrong. Probably didnt help you any but just thought I would share my experience and fix when I was in the same position.
Sent from my SGH-I317 using xda premium
Both of you are good people. Alleviated is a drastic understatement. Was afraid it was a bad internal storage (bad hard drive) and was an issue limitec to my device. Others have done it, it can be fixed.
Cheers, gonna odin reflash now. If not will figure it out.
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2
Let me know im always ready to help and trouble shoot had lots of devices and theyve all lived through my tests and bad flashes :thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Keep us posted.
Sent from my SGH-I317 using xda premium
jdc5 said:
Keep us posted.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Help full group over here, Appreciated greatly. Ive messed up a couple devices pretty good in my day, but never beyond repair. Always credited to people round these forums.
The factory reset didnt seem to help. But if system apps are missing... Reflashed the original tar file, and am just sitting here with a lump in my throat watching the Samsung logo hang...
Anyone got a link for the original rogers firmware?
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2
*edit* back to stock. Dont wanna speak too soon, kinda superstitious with phones. But i think im good. Took two trys to flash original firmware.
Thanks guys, **** not so bad when ya got communication in a forum.
Cheers
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2
What I did when it was stuck at the Samsung logo was I took out the battery> held down volume up, center home, and power to go into the system and did a factory wipe> then it pulled through nack to stock. Give it a try and keep me posted.
Sent from my SGH-I317 using xda premium
I tried the factory wipe through the cwm recovery included, didnt work. Was still stuck on samsung logo. Reflashed with odin a second time which allowed a successful boot and recovery of my paranoid android backup. Im good to go... Gonna do some more reading though. Im missing something important with this phone. Moving from 4.1 to 4.2 roms or vice versa seems to be... Weird.
Anyways all good. Thanks.
Sent from my SGH-I317 using Tapatalk 2
Sent from my SGH-M919 using xda app-developers app
rp56 said:
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
I have TWRP. I used to use CWM, but ever since getting my G4, that was what was only avail at the time. I really have to complaints on it though...other than the navigation from forlder to folder was easier on CWM.
Cwm is rock solid. Twrp has bugs(backup/restore especially) and lacks dev support.
Sent from my Nexus 4 using xda premium
Since OUDHS is based off CWM (IIRC), I'll have to say that. For the most part I've used CWM without problems anyway.
If you are using roms bssed off cyanogenmod... I say CWM but if your using TW roms go with TWRP
Sent from my SGH-M919 using xda premium
Wow. Didn't expect these comments. Here's my 2 cents. I started with cwm on my DX, then got touch cwm, then started to do aosp on all my phones really started with the gnex. Once I got my gnex ran aosp ever since. Have 3 s3,s as well. Twrp all the way. Never had issues and last checked it was faster. But then again. I haven't used cwm in years
Sent from my SGH-M919 using Tapatalk 2
I tried all three on touchwiz and twrp seems to work best for me.
Sent from my SGH-M919 using Tapatalk 4 Beta
I prefer TWRP, used to use CWM and it never failed me, so I will not complain, it's a preference. My bigger question would be, how would I move a file in recovery to another recovery if I wanted to have a few recovery options? Example, have the original backup on OUDHS and then switch to TWRP, how do you move that file? Sorry, not trying to hijack, but this thread seems like a good place for this kind of a question.
Had alot issues with twrp restoring nands, I went to cwm on my s3.
Twrp it points to backups that get put into the "0 "partition instead of the way it used to let u restore from external sd...in my opinion the multiple user partitions that now get created in custom recovery since jellbean is a huge headache. .. ive lost plenty of backups.. and no thanks to flashing cm10, downgrading to move all info back to internal storage is a train wreck ... I hate the way it is all set up now ..
Twrp benefit is its touch based and u can name your backups.
Cwm seems better but not as pretty.
Sent from my SGH-M919 using xda premium
---------- Post added at 09:44 AM ---------- Previous post was at 09:43 AM ----------
gear79 said:
I prefer TWRP, used to use CWM and it never failed me, so I will not complain, it's a preference. My bigger question would be, how would I move a file in recovery to another recovery if I wanted to have a few recovery options? Example, have the original backup on OUDHS and then switch to TWRP, how do you move that file? Sorry, not trying to hijack, but this thread seems like a good place for this kind of a question.
Click to expand...
Click to collapse
Anything done from one recovery is not compatible with the other.. for instance as far as I know u can not restore a twrp backup with cwm and vise versa
Sent from my SGH-M919 using xda premium
lojak29;42028562
[/COLOR said:
Anything done from one recovery is not compatible with the other.. for instance as far as I know u can not restore a twrp backup with cwm and vise versa
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Easiest way, save a backup with each recovery, that way, when the need arises to switch recoveries, you have it saved.
gear79 said:
Easiest way, save a backup with each recovery, that way, when the need arises to switch recoveries, you have it saved.
Click to expand...
Click to collapse
That sounds like a lot more work (and space?) than it's worth!
lordcheeto03 said:
That sounds like a lot more work (and space?) than it's worth!
Click to expand...
Click to collapse
True, but it is an option, and when I needed it (due to a different recovery) I was in a jam, I had to wait til I got to my home computer. I have now uploaded all my recoveries to DropBox. I have a 32gb sd card, so space is of no real problem for me at this time.
gear79 said:
True, but it is an option, and when I needed it (due to a different recovery) I was in a jam, I had to wait til I got to my home computer. I have now uploaded all my recoveries to DropBox. I have a 32gb sd card, so space is of no real problem for me at this time.
Click to expand...
Click to collapse
Good point. I've been meaning to sync a bunch of stuff to my dropbox, but with upload speeds of less than 1Mbps, it's easy to procrastinate doing that.
lordcheeto03 said:
Good point. I've been meaning to sync a bunch of stuff to my dropbox, but with upload speeds of less than 1Mbps, it's easy to procrastinate doing that.
Click to expand...
Click to collapse
Try and edit and change your apn settings to back to hspa+
My thread in general explains how and why ...you may gain a mb or 2 on upload there's no real fix for faster uploads, but u will get huge increase in megabytes on the download side.
I always use wifi for dropbox uploads.
Sent from my SGH-M919 using xda premium
lojak29 said:
Try and edit and change your apn settings to back to hspa+
My thread in general explains how and why ...you may gain a mb or 2 on upload there's no real fix for faster uploads, but u will get huge increase in megabytes on the download side.
I always use wifi for dropbox uploads.
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
Ohh no, it's nothing to do with my APN settings; it's the area which I live. I'm on AT&T service, and within about a 20 mile radius of my home I'm on EDGEand spotty 3G. My home internet is only 2Mbps down/ .25 up, so that's out too. It's just a case of bad location.
But thanks anyway!
Cwm but at the time twrp was only available. Twrp had crashed several times on my tablet while loading roms. But no issues so far on my phone.
Sent from my SGH-M919 using xda app-developers app
lordcheeto03 said:
Ohh no, it's nothing to do with my APN settings; it's the area which I live. I'm on AT&T service, and within about a 20 mile radius of my home I'm on EDGEand spotty 3G. My home internet is only 2Mbps down/ .25 up, so that's out too. It's just a case of bad location.
But thanks anyway!
Click to expand...
Click to collapse
So u are on att sim withba Tmo s4? Or att branded s4, just confused why u wasnt in the att forums
Sent from my SGH-M919 using xda premium
lojak29 said:
So u are on att sim withba Tmo s4? Or att branded s4, just confused why u wasnt in the att forums
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
TMO S4 on AT&T service... I jump around between the two, whatever peaks my interest I read/reply.
I prefer TWRP. I've never had a problem with it, very reliable. In my experience, it is very well supported and updated frequently. Not to say CWM is bad, it always worked for me as well.
TWRP for me!
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
If its boot looping that's not normal obviously you know that so I would exchange it. Keep swapping until you get a good one.
Sent from my Nexus 7 using Tapatalk 4
Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
wha?? I would return immediately.
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Will try that. Thanks!
Sent from my SPH-L710 using xda premium
player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thought I'll give you an update.. Installed CM10.2 for a few days, as you said.. No issues what so ever. Decided to try my luck with CoolRom and it bootlooped the moment I rebooted.
Decided on doing a complete wipe of the device and flashing a factory rom ( http://forum.xda-developers.com/showthread.php?t=2381582 ).
Don't want to give up hope yet.
Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Rooted it for some apps that required root access.
smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There are tons of apps that require root access and are mandatory for many people including me.
I wouldn't bother to unlock and root. The N7 is flawless and fast out of the box.
Sent from my Nexus 7 using xda app-developers app
Again, root access is required for most decent backup programs and cloud data syncing apps. The issue doesn't require a debate about whether you need root or not. Yes the N7 is wicked fast and if you only use it as a bathroom reader for Facebook and light use, then that's cool. I like OTG support for my thumb drives when I'm in the field working.
Glad CM is working for you. That at least shows it isn't a hardware problem. I'd reflash stock images and see where that leaves you. Worse case you use CM (oh my!) until we see a patch.
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
You also should do a complete wipe between stock and CM and AOSP and vice versa. It typically bootloops if you dirty flash one type of rom over another. Stock and AOSP are pretty much the same thing but some custom ROMs like CM have different structures that hose you.
Sent from my Nexus 7 using XDA Premium 4 mobile app
player911 said:
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Mine bootlooped today. Stock. No root or anything. I was forced to do a factory reset from recovery. Very troubling that this seems to be happening to a few people. There's a couple of threads over on android central of people having the same problem.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I will admit this device is great without root but I prefer custom ROMs and titanium backup
Sent from my HTC One using XDA Premium 4 mobile app
Just sat here rebooting the n7 a few time and it happened. Held power and got it to re start the boot process and it loaded. As soon as I unlocked it I got an android process media force close
Sent from my Nexus 4 using XDA Premium 4 mobile app
Andro_pty said:
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Click to expand...
Click to collapse
I rather not do the whole process of sending, receiving, ect. Call me lazy or whatever. Either way, it seems like my problem is solved, I'm once again happy.
Sent from my SPH-L710 using xda premium
Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Super glad its worked. It worked for me. It worked for another guy. And worked for you. I think there is a bad rom image flashed on all of these that are causing lots of problems. The only fix is to clean slate and reflash the stock image, or move to custom ROMs.
Probably need to get someone to write a little app that just automates flashing the stock image again just for simplicity.
I'll probably create a new thread covering this.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
The stock images and the install script .bat file is simple enough.
Especially if you're rooted already. Since you already have the drivers installed on your computer.
Toolkits need to die a slow painful death.
You need root access a pen drive using an OTG cable, install app like titanium backup etc. Rooting doesn't mean custom rom or kernel
Sent from my Nexus 7 using xda app-developers app