Hey guys, so I just have a question. I've read that rom flashes always go to the inactive slot right? So how do you go about wiping your system partition correctly? Do you have to change to the inactive slot to wipe system and then back to your active to flash the rom(which would go into your inactive)?
Not something I can test quite yet, no roms for this device yet but it's good to know before trying. Thanks guys!
H4X0R46 said:
Hey guys, so I just have a question. I've read that rom flashes always go to the inactive slot right? So how do you go about wiping your system partition correctly? Do you have to change to the inactive slot to wipe system and then back to your active to flash the rom(which would go into your inactive)?
Not something I can test quite yet, no roms for this device yet but it's good to know before trying. Thanks guys!
Click to expand...
Click to collapse
If u flash a rom, it goes onto active slot. If u flash an ota zip, it goes to opposite slot. U have basically 2 of every partition. System a and system b etc and so on. If u go to wipe in twrp and wipe system that wipes the system of the slot u are on. Then if u wanna wipe both systems wipe on a, hit reboot button, swap to other slot, wipe system. Its like two phones in one, they did this to allow seamless updates.. cuz if u update ota, it downloads and installs to the inactive slot in case it fails, that way u still have a working system
I unlocked and rooted my phone on day one.... today I applied the new update and it is stuck at the white balls circling the red ball... I figured maybe it needed some time, so I left it in the charger and went to work.... come home... still stuck.
any ideas are welcome.
rsunde said:
I unlocked and rooted my phone on day one.... today I applied the new update and it is stuck at the white balls circling the red ball... I figured maybe it needed some time, so I left it in the charger and went to work.... come home... still stuck.
any ideas are welcome.
Click to expand...
Click to collapse
Try flashing magisk with it
Logan0829 said:
Try flashing magisk with it
Click to expand...
Click to collapse
That worked perfectly!!!!
rsunde said:
That worked perfectly!!!!
Click to expand...
Click to collapse
Coolio
jacksummers said:
If u flash a rom, it goes onto active slot. If u flash an ota zip, it goes to opposite slot. U have basically 2 of every partition. System a and system b etc and so on. If u go to wipe in twrp and wipe system that wipes the system of the slot u are on. Then if u wanna wipe both systems wipe on a, hit reboot button, swap to other slot, wipe system. Its like two phones in one, they did this to allow seamless updates.. cuz if u update ota, it downloads and installs to the inactive slot in case it fails, that way u still have a working system
Click to expand...
Click to collapse
Thanks! So let's say I'm not slot A. If I wipe system and data and install a new rom, with TWRP, ALL of this happens on slot A?
H4X0R46 said:
Thanks! So let's say I'm not slot A. If I wipe system and data and install a new rom, with TWRP, ALL of this happens on slot A?
Click to expand...
Click to collapse
Exactly
Related
Hi all.
Followed the guide on here:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
Rooting wasnt a problem, installing the RA wasnt a problem.
It took awhile to get the phone detected in windows through the USB Debugging mode.
Flashed it using the update-cm-5.0-N1-beta3-signed update.
Now its stuck on the screen thats flash ....
Just keeps doing it over and over. WTF is happening?
Any ideas please.
Thanks
nyzrox said:
Hi all.
Followed the guide on here:
http://androidandme.com/2010/01/hacks/video-how-to-unlock-and-root-a-nexus-one/
Rooting wasnt a problem, installing the RA wasnt a problem.
It took awhile to get the phone detected in windows through the USB Debugging mode.
Flashed it using the update-cm-5.0-N1-beta3-signed update.
Now its stuck on the screen thats flash ....
Just keeps doing it over and over. WTF is happening?
Any ideas please.
Thanks
Click to expand...
Click to collapse
Did you wipe?
pjcforpres said:
Did you wipe?
Click to expand...
Click to collapse
Dont know how to.
Ok detailed instructions.
You rooted and loaded Amon's recovery.(clearly being you flashed beta 3).
Did you Nandroid back up before you flashed as the directions said?
If so, you can simply restore that. and Phoen should be good.
If not,
boot back into Amon's recovery. Hold down volume thing as you click power, to get bootload, then scroll to recovery..
In Amon's recovery, you need to Wipe, Then flash Cyan's beta 3 which should be located on the top level of you SD card.
IN future. ALWAYS do Nandroid backup. I'm new, but when i screwed up i could just restore really easily. Avoided alot of pain/stress that way.
If you still end up having trouble, we can chat via some instant messenger or something.
seanowns said:
If you still end up having trouble, we can chat via some instant messenger or something.
Click to expand...
Click to collapse
PM Me your msn or AIM please.
nyzrox said:
Dont know how to.
Click to expand...
Click to collapse
Using Amon's RA, there are a list of options, one of them is "wip", open that up and it will give you a list of things to wipe. You will want to "wipe data", "wipe dalvik-cache" and "wipe ext"... then, go to SD card and repair your ext.
Now would be a good time to add in an ext file to your SD card if you want to use apps to SD card... you cand do that in Amon's recovery as well under the SD option, just select "partition SD card FAT32, ext2" and follow the insturctions... then I would recommend selecting the "upgrade ext2 to ext3" option afterwards.
Once you have done all the wiping, partitioned your SD card, do 1 more "wipe data" for good measure, then flash CM's 5.0 beta, then flash the google apps pack, then reboot and you should be good to go.
pjcforpres said:
Did you wipe?
Click to expand...
Click to collapse
nyzrox said:
Dont know how to.
Click to expand...
Click to collapse
I just lol'd.
I didnt see the Wipe option under flash from SD thats all
if you dont wipe first before installing new rom then this will happen to you.
i had the same problem and i wiped it and re-installed and it worked perfectly
theres a "wipe" option when you in the recovery boot image
Its all ok now. I got worried and flashed standard rom back using 'fastboot flash system system.something'
Then it booted fine, so turned off. Went into the bootloader, then down to recovery and saw 'Wipe'
Haha
haha, i am curious to know if anyone has managed to brick their N1 yet?
I tried 2 ROMs: Alliance and Extreme Debloat. If I try to turn off the phone it gets stuck at the booting down logo. This happens when I try to restart it, when I try to boot into SafeStrap, or any other way I attempt to power off the phone.
If I pull the battery & boot up, at the SafeStrap splash screen, even when hitting the "Recents" button it does not let me get into SafeStrap.
How do I fix this? What's the cause?
Haloman800 said:
I tried 2 ROMs: Alliance and Extreme Debloat. If I try to turn off the phone it gets stuck at the booting down logo. This happens when I try to restart it, when I try to boot into SafeStrap, or any other way I attempt to power off the phone.
If I pull the battery & boot up, at the SafeStrap splash screen, even when hitting the "Recents" button it does not let me get into SafeStrap.
How do I fix this? What's the cause?
Click to expand...
Click to collapse
Odin back to stock, re-root and try it again. I'm not sure what causes this but it happened to me a few times with my old Note 3 and SafeStrap.
Misterxtc said:
Odin back to stock, re-root and try it again. I'm not sure what causes this but it happened to me a few times with my old Note 3 and SafeStrap.
Click to expand...
Click to collapse
Doing this now. Thanks for the prompt reply.. I've been going insane
How I rooted originally: Installed towelroot successfully, then installed safestrap, booted into recovery, backed up system, created ROM slot #1, and installed a ROM.
Did I do something incorrectly?
edit: p.s. nice avatar
Haloman800 said:
Doing this now. Thanks for the prompt reply.. I've been going insane
How I rooted originally: Installed towelroot successfully, then installed safestrap, booted into recovery, backed up system, created ROM slot #1, and installed a ROM.
Did I do something incorrectly?
Click to expand...
Click to collapse
Not really but I stay away from ROM slots because there is a bug with having to pull the battery on reboot. Re-download the latest SS because the first one had a problem with memory corruption witch sounds like happened to you. If you can get into stock recovery try clearing cache or factory resetting from there. Either way you will have to reset. It's safe to flash to the stock slot as long as you have a good backup.
Edit: Thanks on the avatar, quite a few people like it. Hopefully it helps someone out.
Misterxtc said:
Not really but I stay away from ROM slots because there is a bug with having to pull the battery on reboot. Re-download the latest SS because the first one had a problem with memory corruption witch sounds like happened to you. If you can get into stock recovery try clearing cache or factory resetting from there. Either way you will have to reset. It's safe to flash to the stock slot as long as you have a good backup.
Click to expand...
Click to collapse
So after I ODIN I should:
1. Re-root
2. Re-download & install SS
3. Backup, then wipe everything & install in the main ROM slot
?
Haloman800 said:
So after I ODIN I should:
1. Re-root
2. Re-download & install SS
3. Backup, then wipe everything & install in the main ROM slot
?
Click to expand...
Click to collapse
Yup, run towelroot and update SU from SS.
Worked perfectly. Thanks!!
Haloman800 said:
Worked perfectly. Thanks!!
Click to expand...
Click to collapse
Cool, I'm glad it worked for you.
So i had the stock rom 4.4.2 not rooted
I flashed the cwm 6.0.4.7 with heimdall
And i tried from the external storage to install cyanogenmod
First at the installation i get an error about loki fying
After rebooting at the galaxy s4 logo up to the left i get small letters kernel is not seandroid enforcing
set warranty bit : kernel.
And although i wiped cache data dalvik and so on. I still have all the old data on my internal storage....
What am i doing wrong?
I am not sure where you are seeing a problem.
Is cyanogen not loading?
The kernel not seandrpid enforcing thing is normal. It means nothing to you in terms of daily use.
Skipjacks said:
I am not sure where you are seeing a problem.
Is cyanogen not loading?
The kernel not seandrpid enforcing thing is normal. It means nothing to you in terms of daily use.
Click to expand...
Click to collapse
since i wiped data cache and so on
i should load the phone and the install should be a clean one... instead of that i have still all my files from the previous rom
phoinixtk said:
since i wiped data cache and so on
i should load the phone and the install should be a clean one... instead of that i have still all my files from the previous rom
Click to expand...
Click to collapse
Not an issue. I have the same thing.
Files remain, but all the settings are cleared..
"If someone helps, never forget to hit thanks ? "
DeepankarS said:
Not an issue. I have the same thing.
Files remain, but all the settings are cleared..
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
yeah ok... so i ll have to live with the weird boot
i just formated from within the phone settings to remove the files...
phoinixtk said:
yeah ok... so i ll have to live with the weird boot
i just formated from within the phone settings to remove the files...
Click to expand...
Click to collapse
You mean like your pictures and stuff? That is because they are on the internal sd card. You don't need to wipe that stuff on a rom install.
I installed the Rom VZW_BOK3_ODEX_DEODEX_V1 after the 3rd or 4th time I rooted it, and now I'm not able to restore to stock rom with odin. or get into safetrap recovery or flash through flashfire and I don't know what else to do, and it's lagging so much, can't install app most of the time, can't open apps after a long time I restarted it. Please help me.
britchel said:
I installed the Rom VZW_BOK3_ODEX_DEODEX_V1 after the 3rd or 4th time I rooted it, and now I'm not able to restore to stock rom with odin. or get into safetrap recovery or flash through flashfire and I don't know what else to do, and it's lagging so much, can't install app most of the time, can't open apps after a long time I restarted it. Please help me.
Click to expand...
Click to collapse
There's no reason you shouldn't be able to restore if you can get into Download mode, unless either your USB port is messed up or the restore image is corrupted. Check the md5 of the stock restore image you're trying to use, and try a different cord and/or a different USB port on your computer.
Also make sure you're not trying to downgrade to BOD5 or earlier if your bootloader is BOE1 or above, because you can't downgrade.
I can get into download mode, if I flash something else via odin works also it flash the .img it's the bok3 I've done it before, but now nothing work and it's hellllll! I also flashed PB1 that is post on the tread.
britchel said:
I can get into download mode, if I flash something else via odin works also it flash the .img it's the bok3 I've done it before, but now nothing work and it's hellllll! I also flashed PB1 that is post on the tread.
Click to expand...
Click to collapse
What exactly happens after you click the button to flash the stock image file in Odin? Odin should say OK and the phone should reboot. What happens after that?
painiac said:
What exactly happens after you click the button to flash the stock image file in Odin? Odin should say OK and the phone should reboot. What happens after that?
Click to expand...
Click to collapse
Indeed, it says ok, then it flash the .img and says successful and it reboot the phone like it should. But, then when it start, it's just like it was before, but without root
Make sure you got installed buisy box and safe strap . Install recovery from ss , go to super su and update and make sure is granting the app . Now install NI2 SS flasher for lollipop and make sure super su grant access . Run NI2 and go in the ss. Full wipe then install whatever rom and whatever match firmware with no bootloader then reboot.
alin919 said:
Make sure you got installed buisy box and safe strap . Install recovery from ss , go to super su and update and make sure is granting the app . Now install NI2 SS flasher for lollipop and make sure super su grant access . Run NI2 and go in the ss. Full wipe then install whatever rom and whatever match firmware with no bootloader then reboot.
Click to expand...
Click to collapse
I did that, and would always get stock on the Samsung screem... ima try again... and update the post in a little.
britchel said:
I did that, and would always get stock on the Samsung screem... ima try again... and update the post in a little.
Click to expand...
Click to collapse
Some time it take 5 minute . try pull battery . if not working, next time you trying to do same think but don't reboot on last step . need to reboot on download mode and flash with Odin https://www.androidfilehost.com/?fid=24052804347768483 that's it should work .
alin919 said:
Some time it take 5 minute . try pull battery . if not working, next time you trying to do same think but don't reboot on last step . need to reboot on download mode and flash with Odin https://www.androidfilehost.com/?fid=24052804347768483 that's it should work .
Click to expand...
Click to collapse
Try booting into stock recovery mode (hold home + vol UP + power), and clear cache from there and then reboot.
If that doesn't work, do the same thing but do "factory reset" from stock recovery.
painiac said:
Try booting into stock recovery mode (hold home + vol UP + power), and clear cache from there and then reboot.
If that doesn't work, do the same thing but do "factory reset" from stock recovery.
Click to expand...
Click to collapse
You are correct, thanks for mentioning that.
alin919 said:
Some time it take 5 minute . try pull battery . if not working, next time you trying to do same think but don't reboot on last step . need to reboot on download mode and flash with Odin https://www.androidfilehost.com/?fid=24052804347768483 that's it should work .
Click to expand...
Click to collapse
So, instead of installing the bike install the one in the link?
britchel said:
So, instead of installing the bike install the one in the link?
Click to expand...
Click to collapse
Bok3 sorry
britchel said:
So, instead of installing the bike install the one in the link?
Click to expand...
Click to collapse
In the link is just the bootloader. Do same thing but not reboot . Put in download mode and flash with odin.
britchel said:
Bok3 sorry
Click to expand...
Click to collapse
In the safestrap , wipe and just flash the rom then the bok3 firmware ( your choice for rom and firmware , bok3 or pb1 ) . When is done and you see the SS home splash just reboot to download mode ( if not working do it manual ) and odin the og5 bootloader just in case https://www.androidfilehost.com/?fid=24052804347768483. Done , wait 5 minute , if not working reboot recovery manual and wipe data , factory reset and cache. Is this clear enough ?
Yes, was CLear enough, but it didn't work...
as the last resource I try to fix it with the Verizon app and also with kies. Both reboot and reset the phone, but it is still laggy and the apps wont open soon but after long time... also will freeze for a long time. do you think have something to do with core system?
britchel said:
Yes, was CLear enough, but it didn't work...
as the last resource I try to fix it with the Verizon app and also with kies. Both reboot and reset the phone, but it is still laggy and the apps wont open soon but after long time... also will freeze for a long time. do you think have something to do with core system?
Click to expand...
Click to collapse
Idk , seems like something is corrupted in your phone . The only think i know to do , try to install one off 5.1.1 rom like pure note 5 ( this is the best for me ), is very good rom slim and fast and see if is make difference .
britchel said:
Yes, was CLear enough, but it didn't work...
as the last resource I try to fix it with the Verizon app and also with kies. Both reboot and reset the phone, but it is still laggy and the apps wont open soon but after long time... also will freeze for a long time. do you think have something to do with core system?
Click to expand...
Click to collapse
A reset will resolve just about any issue caused by software. You might be looking at a hardware issue.
Install a system monitor app of some kind to see if any processes are really busy.
It's a long shot, but the only thing that comes to my mind is to remove the microSD card: if that resolves the issue, it means your processor is busy chewing on indexing all the media files on your microSD card and may be getting hung up on a corrupted file. If that does nothing, you might have bad RAM or something.
painiac said:
A reset will resolve just about any issue caused by software. You might be looking at a hardware issue.
Install a system monitor app of some kind to see if any processes are really busy.
It's a long shot, but the only thing that comes to my mind is to remove the microSD card: if that resolves the issue, it means your processor is busy chewing on indexing all the media files on your microSD card and may be getting hung up on a corrupted file. If that does nothing, you might have bad RAM or something.
Click to expand...
Click to collapse
Thanks, antutu it's fine?
And maybe the SD card as it won't read it fast.. and when I try to access to the SD it maybe freEze or slow down... I'll check it out
Yes, for being slow I'm pretty sure was the SD car as I removed it and it feels more smooth, do you know if there is a way to keep the SD in the phone?
britchel said:
Yes, for being slow I'm pretty sure was the SD car as I removed it and it feels more smooth, do you know if there is a way to keep the SD in the phone?
Click to expand...
Click to collapse
First, try opening the SD card on your computer and searching for files of size "0 kb", (that's zero). If you see any media files that are zero kb, delete them. They are corrupted and are causing your phone's media indexing to get stuck in a loop. Symptoms of this issue are slow performance and the phone running hot from trying to process the file continuously. A battery-use examination or performance monitoring app will reveal "android media process" as the offender.
If this does not resolve the issue, you need to take more extensive action. First, copy everything on the SD card to your computer, then format the SD card using the phone, and then copy the data back to the freshly-formatted SD card. Then double-check it for files with a "0 kb" size.
If the problem persists, a last resort would be getting a new microSD card.
!!! I apologize if this is the wrong thread to ask for help and kindly request that a moderator move it, because I don't know where it's supposed to go and my brain is in panic mode right now, thank you. !!!
So, here goes:
DEVICE INFO: SM-J510FN, TWRP, stock ROM, encrypted data partition
ISSUE: Phone does not boot. Powering it on makes it boot to recovery. Selecting "Reboot to system" from inside the recovery, also boots back to recovery. Cannot mount data partition as it is encrypted (but it doesn't at least ask for PIN or anything, just cannot select /data in mount).
HOW IT HAPPENED:
1. I encrypted the phone while it still wasn't rooted.
2. I flashed TWRP (via Odin) and SuperSU (via TWRP)
3. Phone booted to system normally, everything OK. Root access, all good.
4. Reboot to TWRP, flashed some blacked out Google Apps (Team Blackout .zip files). I got no error message, just "cannot mount data" at some points.
5. I selected "wipe cache and dalvik cache"
6. Reboot to system
Reboot to system doesn't work. It boots back into TWRP!
Now I don't know if the flashing of the .zip apps or if the wiping bricked the phone as I don't have that deep of an understanding of how it works. If you can enlighten me , I'd really appreciate it.
FEAR: That the phone is bricked forever and that I won't be able to format the data partition as I cannot even mount it and TWRP needs it mounted in order to wipe it (as far as I know). In short, phone ruined forever because of my stupidity.
HOPE: That someone will tell me a way to re-flash the stock firmware or any ROM so that I get the phone to boot up normally.
I really really need help ASAP because this phone does not even belong to me. My employer gave it to me as a gift, provided I use it for work. That's the reason it's encrypted, he wanted it encrypted in case it gets stolen. Now you're probably thinking "why would you root a company phone??" Well it's not a company phone, it is my main phone, my daily driver. It was given to me by my employer, who said I can do whatever I want with it, as long as it remains functional (at work I use it simply for phone calls, WhatsApp, Skype, mail etc)
I assume that I won't sleep much tonight, will try everything to get the phone to boot. But first I'm going to wait for any piece of advice!
Thank you in advance for any feedback...
Can you get into download mode?
If so, you should flash your stock firmware.
Yes if you boot into download mode you can flash stock rom and all will be good
capsLock1337 said:
Can you get into download mode?
If so, you should flash your stock firmware.
Click to expand...
Click to collapse
pando504 said:
Yes if you boot into download mode you can flash stock rom and all will be good
Click to expand...
Click to collapse
Hello, thanks for the replies.
Yes, download mode works. I will download the stock firmware and flash it via Odin then, yes?
But what happens with the encryption then? Will it remain in place and I will just have to enter my pin to boot as usual?
Can you please explain to me why it does not boot now..? As far as I understand, the boot partition couldn't have been damaged. Aka, stock ROM still in place, only difference is it's rooted.
bi11ie said:
Hello, thanks for the replies.
Yes, download mode works. I will download the stock firmware and flash it via Odin then, yes?
But what happens with the encryption then? Will it remain in place and I will just have to enter my pin to boot as usual?
Can you please explain to me why it does not boot now..? As far as I understand, the boot partition couldn't have been damaged. Aka, stock ROM still in place, only difference is it's rooted.
Click to expand...
Click to collapse
Not sure bout the encryption, if you lose it, you can set it up again.
Something went wrong when you tried to flash the blacked out google apps, I honestly don't have a clue.
Good luck
capsLock1337 said:
Not sure bout the encryption, if you lose it, you can set it up again.
Something went wrong when you tried to flash the blacked out google apps, I honestly don't have a clue.
Good luck
Click to expand...
Click to collapse
Haha I really don't care about the encryption at all! I'm just afraid it is going to interfere somehow but hopefully not.
I'm waiting for the stock firmware to get downloaded from sammobile. I know, I know, I should have done that first before anything else, but I was in such a hurry and I thought "OK, this is routine by now, nothing can go wrong", somehow completely forgetting about the encryption. Oops. In any case, I will post the results here later and will be VERY VERY prepared and organized in the future :'(
bi11ie said:
Haha I really don't care about the encryption at all! I'm just afraid it is going to interfere somehow but hopefully not.
I'm waiting for the stock firmware to get downloaded from sammobile. I know, I know, I should have done that first before anything else, but I was in such a hurry and I thought "OK, this is routine by now, nothing can go wrong", somehow completely forgetting about the encryption. Oops. In any case, I will post the results here later and will be VERY VERY prepared and organized in the future :'(
Click to expand...
Click to collapse
How did it go?
capsLock1337 said:
How did it go?
Click to expand...
Click to collapse
I'm flashing right now Let's see if it boots...
*fingers crossed*
Case solved
bi11ie said:
I'm flashing right now Let's see if it boots...
*fingers crossed*
Click to expand...
Click to collapse
Ahh turns out I almost freaked out for nothing! All good! So, for documentation purposes:
1. I flashed stock firmware through Odin
2. Boot up started normally ("firmware update") - got asked for encryption pin!
3. Decryption took a long time, system booted normally - ALL DATA INTACT
4. No root and No recovery (not even stock recovery)
5. I flashed TWRP through Odin and SuperSU.zip
6. Phone booted normally, TWRP there, SuperSU app there.
The only change is that the bloatware I removed is back
I'm so glad it was nothing after all! I was honestly SO scared that I bricked it ^^;
Thanks and sorry!
bi11ie said:
Ahh turns out I almost freaked out for nothing! All good! So, for documentation purposes:
1. I flashed stock firmware through Odin
2. Boot up started normally ("firmware update") - got asked for encryption pin!
3. Decryption took a long time, system booted normally - ALL DATA INTACT
4. No root and No recovery (not even stock recovery)
5. I flashed TWRP through Odin and SuperSU.zip
6. Phone booted normally, TWRP there, SuperSU app there.
The only change is that the bloatware I removed is back
I'm so glad it was nothing after all! I was honestly SO scared that I bricked it ^^;
Thanks and sorry!
Click to expand...
Click to collapse
No need to apoligize, we all do stupid mistakes sometimes
Glad that it worked!