Related
So I just bought this phone, came in Monday, got it activated the same day, was excited! I had many Android phones and rooted without any problems. This one was far easiest the root. I had the stock ROM of course, followed the easy bootloader unlock method, bam! Phone fully unlocked! Fast boot and ADB were openly available, used ADB to reboot into bootloader again to flash CMW with fast-boot. Sweet, now I have recovery! That was a lot less painful process then I had with any phone. After reaching the recovery menu via ADB reboot recovery, I flashed SuperUser for root, and was cheering in victory, then did a clean factory reset to start using my phone as if new (with SU and CMW). At this point I had no idea I could access CMW without a computer (which I should I knew I could after so many roots and unlocks), and this option for a extended reboot to recovery menu was infront of me, waiting to be flashed. http://forum.xda-developers.com/showthread.php?t=1884282 .
Now, I went ahead and try to flash this zip for those extended options, and that is where I went wrong. The zip file screwed my phone so that it would get stuck on the Sprint Logo, and then I realized I forgot to make a nandroid backup. I went ahead and try to fix it, I didn't want to deoxed my phone, wanted to keep it as Factory OEM as possible. Look a glance at the guy's update script, and realized he removed a necessary .odex file and did not include it in the stock power menu to flash back to normal, so now I was stuck w/o that necessary .odex file and a phone that gets stuck at the sprint loading screen. At this point I was still okay, but was questioning this uploader's work, he never mentioned that a deoxded was needed, and his "stock" wasn't stock, it was deoxded without the .odex.
I wanted to clean the "contamination" and start over without a clean untouched ROM, which was a terrible idea. Still forgetting to make a nandroid backup though, and went ahead and found a system dump and system images (system.img.ext4, etc), did a FULL Wipe with (no nandroid backup!) And now my system partition and user data partition in wiped clean. Of course I tried flashing the system.img.ext4 and userdata.img.ext4 and what not with fastboot to get back to clean slate but that wasn't the case. Now I got stuck on WARNING BOOTLOADER UNLOCKED, and it will not even go to a sprint logo boot.
Now I realize I never made a nandroid backup, and kept putting myself in a bigger hole without making one from the start. I tried everything, fastboot flashing, I even make a system.zip update file for CMW to copy a system dump directly to the system partition, phone boots up, flickers, goes to CMW (thought that was going to work for a second). Now I'm stuck with a semi-bricked phone not-so-brand-new-anymore Motorola Photon Q, desperately searching for a way to flash it back in working order.
I have tried and flash various system dumps from users to no avail, and there not any full roms available that can get me out of this mess. Is it anyway method I'm missing to flashing these system dumps to get my phone back online, or will I be stuck without a phone until a rom comes out? I have been using these provided dumps
http://forum.xda-developers.com/showthread.php?t=1856456
http://forum.xda-developers.com/showthread.php?t=1874359 (Bought a Hotfile prem to download this, regular was taking forever, I could reup on my faster FTP if someone wants to give it a shot).
Please help if you know a way to get my beloved phone online! I only had it for a day and I'm in love with it, have no idea where I don't hear more about this awesome phone, I was sold when I saw it in the sprint store. (Reminds me of my old galaxy s1, it was a champ!)
*EDIT*
Problem solved! Thanks arrghhh for his backup files!
1. Use fastboot to flash TWRP to recovery.
2. Make a folder and put these files in that folder!
https://dl.dropbox.com/u/12691845/system.ext4.win
https://dl.dropbox.com/u/12691845/system.ext4.win.md5
https://dl.dropbox.com/u/12691845/boot.emmc.win
https://dl.dropbox.com/u/12691845/boot.emmc.win.md5
3. Place this folder in the following directory.
[Root_of_SD_card] / TWRP / BACKUPS / T0695022LP / [your folder] ( so if your folder is called "argh_restore", it should be found in [Root_of_SD_card] / TWRP / BACKUPS / T0695022LP / argh_restore ) , and inside that folder, the files you downloaded.
4. Boot into recovery, I assume you know how to do this since you unlocked your bootloader to mess up your phone in the first place .
5. TWRP should load, press restore, your folder should show up, select it, select system and boot, enable MD5 checking, and restore your phone.
**IF YOUR FOLDER DOES NOT SHOW UP, directory may be incorrect. You can make a backup and see where it goes to figure out where to place your backup folder!
6. Reboot your phone, your good to go!!
PS. This backup is NOT CLEAN stock! It is stock with deoxed, battery & toggle mod, and extended menu mod, I BELIEVE. Those are the only mods really available so that's my assumption, but arrghhh may know since it is HIS backup that he provided. So far, I've been using phone all day, seems to be running well. Just like stock! Also, I can't forget, shabby's awesome SuperUser mod for root! (You won't need CMW since you have TWRP, but if you want to swtich recovery, thats up to you. CMW is most popular recovery but TWRP is really great as well)!
I'd say you're going to NEED a nandroid backup to restore...
I was hoping flashing the de-odexed would work for ya. Would a nandroid backup of the system partition work? Hopefully it does, because that's about all I can think of to provide for you...
And lesson learned, I hope. Anytime, you do ANYTHING in recovery - MAKE A BACKUP!!
Edit - I re-read your post, did you try flashing the full de-odexed version? Seems like you have some hatred of it, lol... but if it saves your butt who cares.
I did flash a odex system dump, a deoxed system dump, and a system.img.ext4 dump to no avail.
But when the issue first occurred after I flashed the new power menu, I never flash the deoxed version to get the new menu to work. I know it was needed the issue but wanted to restore the original odex. I wanted to keep the phone system as OEM as possible (had some bad experience with modding to much, things don't work they way they use too). I could have done that to fix the issue before, but since I wiped it won't make a difference now (formatted /system /data /cache in CMW).
A Nandroid backup should definitely work I can though!!!!
If I can use someone working Motorola photon Q Nandroid backup I should be able to do a restore all of the system files I wiped (I'm not sure if any other partition other then the /system in the Nandroid backup would have to be restored to get the phone working, I know there /data but I think /system adds the files on first boot to /data?). I can still fully boot into recovery/fastboot but just need recover the system files back.
Sorry to hear you had problems i have supplied links in previous posts to all files Deodexd and back to original odex
PhotonQ stock Deodexd
PhotonQ stock Odexd
hope one of these help you get going
Yea, I meant try flashing the de-odexed version... even now after you're busted. Rangerbry kindly posted both tho. Hopefully that gets you back in business.
Just read he formated /system tho i can upload all that unless someone beats me to it
Sent from my XT897 using Tapatalk 2
Rangerbry said:
Just read he formated /system tho i can upload all that unless someone beats me to it
Click to expand...
Click to collapse
I get that he wiped /system. I thought what you posted would restore that? I guess not "all" of it eh?
I can take a nandroid backup of /system, but at this point it's been modified - it's far from OEM...
I have a few old nandroid backups, but I don't know if I kept the completely stock one. I should have in retrospect, so I'm going to hope I can find it...
Edit - the only backup of /system I have is a .win file for TWRP... sorry.
If it works I'll take it! lol. Stock would be nice but I have no choice at the moment. I could use a modded rom until a stock rom comes out, just don't want to be with a paper weight lol. I'm trying the Photon Q stock Odexed.zip right now though.
I have a full stock pull i keep on hard drive but cant get it till after work
Sent from my XT897 using Tapatalk 2
Ya may need full stock pull, flashed odex with no avail .
SleepyPanchoo said:
Ya may need full stock pull, flashed odex with no avail .
Click to expand...
Click to collapse
Well here's the system.ext4.win file and the md5.
Not sure if it'll work for you at all, since the file was extracted using TWRP, and you are on CWM... I looked at my CWM backups, and I didn't take a full CWM backup it seems :/ At least I can't find it...
I know shabby has stock images pulled from the Motorola Photon Q here : http://forum.xda-developers.com/showthread.php?t=1856456
I did fastboot flash the system.img.ext4 (523 mb - seems like a full system image!) he has provided to no avail. But I'm thinking it should have worked? Its looks like a full system.img that should write all the necessary data to the /system partition to get me going, unless I have to rename system.img.ext4 to system.img before flashing, I'd have to get that a try and see if that makes a difference.
I can give that try as well and see that will fix my phone. Thanks for all the help you guys are giving me. I thought I was alone!
SleepyPanchoo said:
I can give that try as well and see that will fix my phone. Thanks for all the help you guys are giving me. I thought I was alone!
Click to expand...
Click to collapse
No prob and last i checked this is XDA no ones ever alone in getting problems fixed here. Still going to be several hrs until i get home tho
Sent from my XT897 using Tapatalk 2
arrrghhh said:
Well here's the system.ext4.win file and the md5.
Not sure if it'll work for you at all, since the file was extracted using TWRP, and you are on CWM... I looked at my CWM backups, and I didn't take a full CWM backup it seems :/ At least I can't find it...
Click to expand...
Click to collapse
Just flashed TWRP 2.2.2.2 gonna give your system.img a shot!
Looks like it help me resotre your nandroid backup of your /system partition, but still doesn't boot. This is the file sizes I see when I go to backup in TWRP
System ( 224 MB )
Data ( 0 MB )
Boot ( 10 MB )
Recovery ( 10 MB )
Cache ( 16 MB )
Don't think data should be 0 MB? Maybe a full nandroid backup would work?
*EDIT*
I'm using shabby's stock images to fastboot flash userdata.img.ext4 but does not seem to have any effect. Data is still the same size. I may need a full nandroid backup to get this phone recovered, guess I will have to wait Rangerbry to upload that backup. hopefully that will work.
SleepyPanchoo said:
Looks like it restored your nandroid backup of your /system partition, but still doesn't boot. This is the file sizes I see when I go to backup in TWRP
System ( 224 MB )
Data ( 0 MB )
Boot ( 10 MB )
Recovery ( 10 MB )
Cache ( 16 MB )
Don't think data should be 0 MB? Maybe a full nandroid backup would work?
Click to expand...
Click to collapse
Did you restore "everything" or what was checked on restore?
I did restored everything but it seems the nandroid backup you gave me was a system-only backup. Data, cache, etc was not included in this backup. I made a backup of my wiped phone and overwritten the empty system backup with the /system backup you provided me, then restored it. Even though system is there phone still gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. I may need a full entire backup (/system /data /boot /recovery /cache), if that doesn't work I'm not sure what will.. :/.
*Maybe Sprint can reflash back to stock or replace?
SleepyPanchoo said:
I did restored everything but it seems the nandroid backup you gave me was a system-only backup. Data, cache, etc was not included in this backup. I made a backup of my wiped phone and overwritten the empty system backup with the /system backup you provided me, then restored it. Even though system is there phone still gets stuck on "WARNING BOOTLOADER UNLOCKED" screen. I may need a full entire backup (/system /data /boot /recovery /cache), if that doesn't work I'm not sure what will.. :/.
*Maybe Sprint can reflash back to stock or replace?
Click to expand...
Click to collapse
Why would you need my /data? Or /cache!?! That doesn't make any sense.
I can provide a backup of /boot and /recovery.
Edit - Hrm... Well, /recovery shouldn't be needed. boot.emmc.win / md5
Wouldn't data have some required files for android to work? I know it contains user data as well (such as apps) but a nandroid backup, factory reset, then 2nd android backup that is given out can be made. Im sure cache is not necessary, but I'm trying everything at the moment, nothing seems to work when it feels like it should...!! I guess I can give your /boot a try. Don't think its /recovery since Im using your recovery now lol.
hi
Ive just installed Cleanrom, and it seems slower than the stock rom i used before.
I wonder if i should have done a system format in cwm, as doing this for Slimbean on my SGS helped quite a bit...
thanks
geoslake said:
hi
Ive just installed Cleanrom, and it seems slower than the stock rom i used before.
I wonder if i should have done a system format in cwm, as doing this for Slimbean on my SGS helped quite a bit...
thanks
Click to expand...
Click to collapse
Format system is when you delete your ROM, if you want a clean install, yeah you should format system. This also depends on what ROM you want to flash. If you're going to flash stock, format system is good. I do it all the time when I flash stock
But I can also do it whatever the rom, right ? I mean if I upgrade from Cleanrom from 3.03 to 3.04, I cannot go wrong doing that ? (although they don't talk about formatting system in the guidelines).
Thank you
Format system is when you delete your ROM, if you want a clean install, yeah you should format system. This also depends on what ROM you want to flash. If you're going to flash stock, format system is good. I do it all the time when I flash stock
Click to expand...
Click to collapse
format system basically deletes all your system apps, which really isn't worth to do in an update from v3.0.3 to 3.0.4 - if it's a big update with many more apps included maybe it's worth, but otherways it's waste of time...
-angel* said:
format system basically deletes all your system apps, which really isn't worth to do in an update from v3.0.3 to 3.0.4 - if it's a big update with many more apps included maybe it's worth, but otherways it's waste of time...
Click to expand...
Click to collapse
System app? When I use twrp it said wipe system removes ROM, I guess on cwm is called format system.
Well, I guess "format system" should format system (=wipe the os i guess), not remove apps...
geoslake said:
Well, I guess "format system" should format system (=wipe the os i guess), not remove apps...
Click to expand...
Click to collapse
Hmmm why don't you use twrp. It's much better haha
Tamaskan said:
Hmmm why don't you use twrp. It's much better haha
Click to expand...
Click to collapse
Guess so, I guess its no problem to overwrite CWM with TWRP (as long as I load the right version, that is, JB as im on Cleanrom Inheritance 2.7.2)...
Format system on twrp and cwm means the same thing.
When you flash any ROM, all it does is place everything in the /system partition, and sometimes a kernel is also flashed.. this partition contains all files that make up android. All the apps that come with roms, all mods, themes, framework.. everything is here.
When /system is wiped, it deletes all these files to make way for a new rom. Most roms wipe system automatically when they get flashed anyway :good:
However, I think that cleanrom 3.0.3 is a dependancy for 3.0.4, this means that 3.0.4 requires the 3.0.3 system files to work properly. Check the cleanrom changelog or install instructions
Sent from my GT-I9100
Nothing happens, it just clears your data.
Tamaskan said:
System app? When I use twrp it said wipe system removes ROM, I guess on cwm is called format system.
Click to expand...
Click to collapse
I'm sorry, I was thinking of /system/app lol
I think the updates should rule that themselves that they delete the unnecessary things of an old version, so it's only recommended if you change your ROM or update to a ROM based on a later Android Version (4.1 to 4.2 or vice versa) or from AOSP to stock...
Otherwise it's just waste of time I think, I never used it and never had problems, so I think it's pretty good ruled in the updater scripts of the ROMs
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Or you could just copy the whole twrp folder to your hdd. thats what I do anyway and restore without a problem.
Yep that would have prevented me ending up in that predicament for sure.
So would not flashing roms. The point of the post is really about what to do if you find yourself in that situation and the value of keeping a cool head and thinking through a solution rationally, using your own resources.
The way I see it is: it's my mess I got into it, how am I going to solve it....
Sent from my HTC One S using xda app-developers app
Lost my Backup
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?
matrixmainframe said:
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?
Click to expand...
Click to collapse
Do what the op says and do a backup and you will know where to put it.
Sent from my HTC One S using Tapatalk 2
Plz HELP!!!
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.
abdullah.imran2158 said:
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.
Click to expand...
Click to collapse
1. wrong forum, if you have a one x device
2. calm down
3. relock your bootloader (fastboot oem lock)
4. download and run latest ruu for your phone (search for a suitable one for your cid and carrier if you are branded)
5. you also can flash a custom sense based rom, which gives you sense back (viper one s or trickdroid or android revolution hd)
6. if you want to flash one of these,dont forget to flash the boot.img too
7. before flashing a rom, wipe system, data and cache 3xtimes to be sure you do a clean install
Thanks Man
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
Thanks Man, been stuck in TWRP for about two hours now, thought I soft bricked my Droid Dna forever. I had a backup, and adb pushed it to the /sdcard directory, but it wouldn't show up in the restore section. This empty-backup method worked fine. Thanks, you saved me $400.:good:
Saved my HTC One!
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
I'd just like to say a MASSIVE THANK YOU for this post! I had a major issue and thought I'd lost my 1-day old HTC One (M7). I wasn't so much panicking as I knew i'd find a way, but a cold sweat had started to break!
The biggest lesson I can take from this is simply this... MAKE SURE YOU BACKUP YOUR ORIGINAL ROM BEFORE YOU DO ANYTHING! It's such an obvious thing, but without this simple step, I'd be in trouble right now as HTC haven't an RUU for my specific device yet (plus I'm on a Mac, making running .exe files more painful still)
What had happened was that as a result of a corporate email policy, I had to encrypt my device. I did this after flashing to a new ROM. Unfortunately after I had done so, the new ROM wasn't playing nicely with Exchange (using native HTC Mail app). Of course the issue here is that when you so into TWRP, you can't see the files to restore (because TWRP is opened before the device asks you for the passcode to decrypt... another learning!). To remove the encryption, I had no choice but to do a full format of the device, so I was basically left with a brick
Anyway, once again, thank you for this post, you just saved me AU$700!
Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
Click to expand...
Click to collapse
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.
:good:
cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.
Click to expand...
Click to collapse
Deleted comment
Hei guys,
Please help!!!! I tried to install MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0 on my HTC One s,i got storage issue. Now my sd card is just 48MB. I have installed TWRP v2.6.3.0 and i did backup before flashing room. I decided to do factory restore by TWRP and wiped OS from MY device.Now when i do backup i get failed error: not enough free space on storage. Total size of all data 203MB, available space 48 MB.I see my sd card on pc through TWRP, but i cannot make backup and even put any new rom into my sd card to flash it because of 48MB...Is it any chance to get back any OS on my HTC One s....?
This post might help
http://forum.xda-developers.com/showthread.php?p=47744972.
Sent from my One S using xda app-developers app
StifflerServices said:
Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?
Click to expand...
Click to collapse
EDIT: oops, somehow thought this was a recent post. Never mind
Not really.
If you are S-off,
Restore Backup,
Wipe Caches
S-On
Restore Backup
Wipe Caches
(if the rom you were previously on had a different Boot.img you will need to fastboot your boot.img) In the backup
Assumes you are not trying to restore a backup to 2.15 if you were just on 2.16. You will need to RUU + factory reset/clear storage for that.
I'm sry not sure what "RUU" means... Probably will remember once u tell me I'm sure. But Ya I kinda just winged it, didn't flash the Rom to do the NanBU and all went fine, which is odd cause on my S2 w cwm it out me in a boot loop and had to start over, but I think TWRP may be a diff setup when restoring nanbu's. But either way it's always nice to know and find a "step by step" guide to restoring NanBU's from previous / updated / or different ROMs. For noobs that was one of the confusing things to do due to lack of that info in threads or utube vids out there.
Got a question. I've made my backup files but restore shows nothing but storage... No files to chose, no more options to restore. Is it normal?
Sent with my One S C2 Sense 5 using Taptalk
brilliant!
ATSPerson said:
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.
metropical said:
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.
Click to expand...
Click to collapse
From one Clash fan to another, thanks for the thanks ☺
¡La lucha continua!
Can i install roms on System 1, who and how? pls help, i dont want to break my phone, i 've LiquidSmooth but on System 3, i need more space and the only way its installing on system 1..
Who other roms can i install on system 1, and who are requirement? thx for your help :good::cyclops:
Yes, you can. In fact, I am using just System 1 (AOSB) as my daily ROM.
I don't know if this is required, but I'm always doing the following:
1. Format /system, /data, /cache
2. Wipe System, Cache, Dalvik Cache
3. Install ROM
4. Install GApps
I never had any problems since.
Goodluck mate!
Cheers,
Rae
I have never used any other system other than system 1 as daily driver..i don't know y ppl are so scared to flash..same time two years back we didn't even have a recovery on boot and still used to flash roms courtesy rdavisct, alteredlikeness, jimbridgman n co..this whole concept of multiple systems has made things more complicated than before it seems
Sent from my MB865 running CaRbOn 4.4.3 source built by dmroeder!!
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
devilhunter47 said:
I have never used any other system other than system 1 as daily driver..i don't know y ppl are so scared to flash..same time two years back we didn't even have a recovery on boot and still used to flash roms courtesy rdavisct, alteredlikeness, jimbridgman n co..this whole concept of multiple systems has made things more complicated than before it seems
Sent from my MB865 running CaRbOn 4.4.3 source built by dmroeder!!
Click to expand...
Click to collapse
To the steps mentioned above
Wipe battery stats
After installation go to system keeper option
Install bmm to main system
Reboot
Safer this way
Sent from my MB865 using Tapatalk 2
Raeshabu said:
Yes, you can. In fact, I am using just System 1 (AOSB) as my daily ROM.
I don't know if this is required, but I'm always doing the following:
1. Format /system, /data, /cache
2. Wipe System, Cache, Dalvik Cache
3. Install ROM
4. Install GApps
I never had any problems since.
Goodluck mate!
Cheers,
Rae
Click to expand...
Click to collapse
Thaankss..! bro im gonna try it now..! i did a back up of stock 4.0.4
devilhunter47 said:
I have never used any other system other than system 1 as daily driver..i don't know y ppl are so scared to flash..same time two years back we didn't even have a recovery on boot and still used to flash roms courtesy rdavisct, alteredlikeness, jimbridgman n co..this whole concept of multiple systems has made things more complicated than before it seems
Sent from my MB865 running CaRbOn 4.4.3 source built by dmroeder!!
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
To the steps mentioned above
Wipe battery stats
After installation go to system keeper option
Install bmm to main system
Reboot
Safer this way
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
ohhh i'm really thankful , i was nervous but with this steps i'm sure of wait i'm going to do..
saga02 said:
Thaankss..! bro im gonna try it now..! i did a back up of stock 4.0.4
Click to expand...
Click to collapse
Good luck mate! :good:
@devilhunter47
Thanks for the additional info.
Anyways, I never install BMM after flashing ROMs because it auto-installs after you press back from Install from Zip. Or maybe we just have different experiences regarding this.
Thank you again! :highfive: :good:
Raeshabu said:
Good luck mate! :good:
@devilhunter47
Thanks for the additional info.
Anyways, I never install BMM after flashing ROMs because it auto-installs after you press back from Install from Zip. Or maybe we just have different experiences regarding this.
Thank you again! :highfive: :good:
Click to expand...
Click to collapse
Sometimes it fails to and i had to fxz
Sent from my MB865 using Tapatalk 2
171
devilhunter47 said:
Sometimes it fails to and i had to fxz
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
guys i've a problem, when the installations finish i did "system keeper option", and then show me a mistake, saying "BBM will not start after reboot", and now the phone dont show me BBM and only restart and restart :/ i dont know what to do now, because i can enter to bbm and fix this :S.. I can not even go to android, is happening and I did wrong? : ( And how to fix this please help ..!
Raeshabu said:
Good luck mate! :good:
@devilhunter47
Thanks for the additional info.
Anyways, I never install BMM after flashing ROMs because it auto-installs after you press back from Install from Zip. Or maybe we just have different experiences regarding this.
Thank you again! :highfive: :good:
Click to expand...
Click to collapse
Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system: (help please
saga02 said:
Heelpp..! BMM not appear, and the phone stayed restarting does nothing but nothing out of the motorola logo screen goes black for a minute and not start, should show BBM but no longer does, and prior to the reboot when installation is complete and I gave keeper system option "Install bmm to main system" not only told me BBM started after reboot and so did not know what to do now ..: S can not access the system 3 is where I have q my other system: (help please
Click to expand...
Click to collapse
Sorry to hear that.
So, are you saying that after you installed a ROM in System 1, you force-installed BMM again through System Keeper?
I think you need to FXZ back to stock ICS, then root, then install BMM from the market again.
I think I had the same experience back when I first got this phone and was still experimenting on stuffs.
Anyways, do you know how to FXZ back to stock ICS? There's a guide on how to do that here:
forum.xda-developers.com/showthread.php?t=1937112
Click to expand...
Click to collapse
You SHOULD follow every step mentioned on the thread, and also download the correct FXZ for your phone.
Or you could check my post here:
forum.xda-developers.com/showthread.php?p=53305693#post53305693
Click to expand...
Click to collapse
Just ignore the part where I insist you should download the AT&T FXZ for your phone. That part is for my phone only.
Raeshabu said:
Sorry to hear that.
So, are you saying that after you installed a ROM in System 1, you force-installed BMM again through System Keeper?
I think you need to FXZ back to stock ICS, then root, then install BMM from the market again.
I think I had the same experience back when I first got this phone and was still experimenting on stuffs.
Anyways, do you know how to FXZ back to stock ICS? There's a guide on how to do that here:
You SHOULD follow every step mentioned on the thread, and also download the correct FXZ for your phone.
Or you could check my post here:
Just ignore the part where I insist you should download the AT&T FXZ for your phone. That part is for my phone only.
Click to expand...
Click to collapse
Ready brother could fix all that I did just now was able to install in system 1 and so far everything is fine, the problem was the gapps and they made the bootlooping, I am LiquidSmooth 3.1 (4.4.3) that I can recommend another rom this stable and fast ... thank you very much for your help really'm super grateful to you ..
saga02 said:
Ready brother could fix all that I did just now was able to install in system 1 and so far everything is fine, the problem was the gapps and they made the bootlooping, I am LiquidSmooth 3.1 (4.4.3) that I can recommend another rom this stable and fast ... thank you very much for your help really'm super grateful to you ..
Click to expand...
Click to collapse
Hey, I'm glad that you fixed your phone. :highfive:
Cheers,
Rae
saga02 said:
Can i install roms on System 1, who and how? pls help, i dont want to break my phone, i 've LiquidSmooth but on System 3, i need more space and the only way its installing on system 1..
Who other roms can i install on system 1, and who are requirement? thx for your help :good::cyclops:
Click to expand...
Click to collapse
Dude you can flash ROM's on System 1 but please be careful as it will delete all other data on the other systems.
One more thing if your using altreds CM 11 use the BaNkS minimal gapps, It's not a problem to flash on the system 1, the thing is a failed flash can sometimes lead to you needing a FXZ, so just be careful on which ROM your flashing. :good:
I have little bit confusion. Please guide if these steps are correct:
1. Using BMM, format system 1 partition, data, cache.
2. Clean/wipe data, cache, battery, dalvik
3. Install ROM and GAPPs in system 1
4. system keeper > keep/install BMM
Are these steps correct?
Another question is if I want to install only one ROM in system 1 and want to use all available space for this setup then how to setup the partitions with maximum available space? Or I don't need to setup partitions?
Jack Sparrow xda said:
I have little bit confusion. Please guide if these steps are correct:
1. Using BMM, format system 1 partition, data, cache.
2. Clean/wipe data, cache, battery, dalvik
3. Install ROM and GAPPs in system 1
4. system keeper > keep/install BMM
Are these steps correct?
Another question is if I want to install only one ROM in system 1 and want to use all available space for this setup then how to setup the partitions with maximum available space? Or I don't need to setup partitions?
Click to expand...
Click to collapse
No need to set partition sizes on system 1, that's solely for multi-booting ROMs on systems 3-6. Everything else is good though.
1BadWolf said:
No need to set partition sizes on system 1, that's solely for multi-booting ROMs on systems 3-6. Everything else is good though.
Click to expand...
Click to collapse
Thanks for the info, that was really helpful
But one confusion, I use BMM for flashing ROMs. And in case of BMM, we have to set partitions for system, data and cache. How to do that partitioning step in case if we want to flash ROM in the system 1 ? Won't we have to specify the sizes for all of those partitions?
Another question is, how to fully clean up the system 1 and free up whole ROM space before starting system 1 setup? I mean can I clean everything which came from factory before flashing on the system one to get as big as possible size of internal ROM for the system 1 setup? How much space we can get by doing that? Right now it shows around 2 GB available for user (apps and data) in the 4GB ROM of the Atrix 2, how much would it show in case of custom ROM flashing by freeing up whole space?
Jack Sparrow xda said:
Thanks for the info, that was really helpful
But one confusion, I use BMM for flashing ROMs. And in case of BMM, we have to set partitions for system, data and cache. How to do that partitioning step in case if we want to flash ROM in the system 1 ? Won't we have to specify the sizes for all of those partitions?
Another question is, how to fully clean up the system 1 and free up whole ROM space before starting system 1 setup? I mean can I clean everything which came from factory before flashing on the system one to get as big as possible size of internal ROM for the system 1 setup? How much space we can get by doing that? Right now it shows around 2 GB available for user (apps and data) in the 4GB ROM of the Atrix 2, how much would it show in case of custom ROM flashing by freeing up whole space?
Click to expand...
Click to collapse
System 1 gets partitioned by flashing the FXZ so it's not necessary to do it with BMM. The best way to clean up system for flashing is to flash the FXZ first, then root and install BMM, etc. You can also use BMM to format system, data, cache and dalvik cache if you haven't created partitions for other systems. The only reason you will ever need to create partitions with BMM is to flash on systems 3-6.
1BadWolf said:
System 1 gets partitioned by flashing the FXZ so it's not necessary to do it with BMM. The best way to clean up system for flashing is to flash the FXZ first, then root and install BMM, etc. You can also use BMM to format system, data, cache and dalvik cache if you haven't created partitions for other systems. The only reason you will ever need to create partitions with BMM is to flash on systems 3-6.
Click to expand...
Click to collapse
Oh, I thought BMM will do it on sys 1 as well. I used sys 3 & 4 just to try out various ROMs without risking the stock system so that I can know which ROM suites me and later I can cleanup the whole system and put that ROM of my liking in the main system.
I am not familiar with FXZ method and it seems more complicated to me. isn't there any way to flash ROM on sys 1 and deleting the other partitions?
I am noob in this flashing thing and its been just 10-12 days since I started it up. the bmm method looked easy to me and I would prefer it if its possible to use for this purpose.
Sent from my MB865 using Tapatalk
Jack Sparrow xda said:
Oh, I thought BMM will do it on sys 1 as well. I used sys 3 & 4 just to try out various ROMs without risking the stock system so that I can know which ROM suites me and later I can cleanup the whole system and put that ROM of my liking in the main system.
I am not familiar with FXZ method and it seems more complicated to me. isn't there any way to flash ROM on sys 1 and deleting the other partitions?
I am noob in this flashing thing and its been just 10-12 days since I started it up. the bmm method looked easy to me and I would prefer it if its possible to use for this purpose.
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Flashing the FXZ is actually pretty simple. The main thing to know is which FXZ is the correct one for your phone. (Also it's a really good idea to find THAT out BEFORE you need it.) BMM is far more complicated and confusing IMHO.
Anyway, it's still possible to do a clean flash via BMM if that's what you're more comfortable with, though, so no worries. Just do a factory reset, which will format data, cache, and dalvik. Since that formats the data partition you will lose everything on any other existing systems. (though it may not always be necessary I normally format the system as well. DO NOT reboot at this point or you'll have no choice but to FXZ.) Then you just flash the zip plus gapps and whatever other mods you want. Personally I like to reboot between flashing each zip. In other words, I flash the ROM then reboot. Then gapps and reboot, etc. No repartitioning is necessary for flashing on system 1 and might actually be detrimental so just skip that.
Thanks a lot @1BadWolf, your post clears all doubts in my mind
1BadWolf said:
No repartitioning is necessary for flashing on system 1 and might actually be detrimental so just skip that.
Click to expand...
Click to collapse
Thanks for letting me know about no need of partitioning sys 1. If I wouldn't have been in this discussion with you, I would have ended up creating partitions on system 1 as well like what I have learnt to do on other systems and there would have been a thread by me on getting stuck in bootloop, you saved me from that.
To be bit on more safer side, let me put what I have understood so far:
1. Boot in BMM.
2. Factory reset on system one. (I have two other custom ROMs on system 3 and 4. will it also clear all the other ROMs installed on other systems also?
3. Format partitions on system one.
4. Clear system, data cache etc
5. Install ROM and GApps on system 1
6. Keep BMM in main system
7. Reboot and done
Is there anything broken or wrong in that chain?
One more query, can I keep continue installing ROMs on other systems like what I am doing right now in case of retaining stock ROM?
I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup Boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img (extract from ap section of downloaded firmware for stock) or install UPie
2. Restore Boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files to /system/system
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.
If anyone can think of another system directory which I can backup and restore please let me know.
physwizz said:
I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img
2. Restore boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.
Click to expand...
Click to collapse
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.
Jeremy_J7 said:
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWinRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.
Click to expand...
Click to collapse
I think the system settings are stored in /data
I'll add it to the list.
physwizz said:
I think the system settings are stored in /data
I'll add it to the list.
Click to expand...
Click to collapse
Test it before you add to the list, can't be giving these people false information bro ?
Jeremy_J7 said:
Test it before you add to the list, can't be giving these people false information bro
Click to expand...
Click to collapse
True
I debloated from here
https://forum.xda-developers.com/galaxy-a20/development/debloat-samsung-a20-variants-t4070957
Then I added the updated camera from Ultimate Pie.
My app folders are here
https://mega.nz/file/dtkkES5L#YfHwWC3rlswwYUeA_cdUESCMQo8rvq8k8n20N-oc-8w
Alright will take a look, is this bootloader specific?
Jeremy_J7 said:
Alright will take a look, is this bootloader specific?
Click to expand...
Click to collapse
Not sure.
If it doesn't work it might reboot into recovery and then you need to copy and paste your own /app and /priv-app folders back in place.
@jajk
Try this
@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?
jajk said:
@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?
Click to expand...
Click to collapse
If you're talking about the red text that talks about 'official binaries' when booting after you flash TWRP (FRP LOCK) then there's a very easy fix.
@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....
jajk said:
@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....
Click to expand...
Click to collapse
I got that because i was using old data
solved by doing a clean install
The data was then good in future
@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different
jajk said:
@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different
Click to expand...
Click to collapse
You didn't restore old data?
Clean install?
@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....
jajk said:
@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....
Click to expand...
Click to collapse
What does red writing say?
@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....
jajk said:
@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....
Click to expand...
Click to collapse
I've had that twice
1. When I forced reboot before UPie was finished installing
2 when I didn't wipe caches , data and system before installing UPie
Could also be Samsung Conspiracy Theorist Detection Program (SCTDP) lol