Hi, I done an advanced rest via TWRP and it wiped my OS. Now it only boots into fastboot, there is no recovery and it is just a loop of the 4 options the phone just restarts for each of them. It is not being recognised in adb devices on my mac. What do i do?
Thanks!
Had the same issue a few weeks ago!
Check here... https://r.tapatalk.com/shareLink?ur...share_tid=3931424&share_fid=3793&share_type=t
Sent from my GM1913 using Tapatalk
berthoff said:
Hi, I done an advanced rest via TWRP and it wiped my OS. Now it only boots into fastboot, there is no recovery and it is just a loop of the 4 options the phone just restarts for each of them. It is not being recognised in adb devices on my mac. What do i do?
Thanks!
Click to expand...
Click to collapse
All you need to is to switch to your other slot and the will boot up.
fastboot --set-active=a
Then try to boot up, if you come back to bootloader.
fastboot --set-active=b
then try to boot up, it will work.
It is highly unlikely that you wipe both your slots.
long as bootloader is unlocked and you can get to fastboot just fastboot flash twrp or oos good luck
Managed to flash the fastboot rom and back working, Thanks!
harpin14789 said:
All you need to is to switch to your other slot and the will boot up.
fastboot --set-active=a
Then try to boot up, if you come back to bootloader.
fastboot --set-active=b
then try to boot up, it will work.
It is highly unlikely that you wipe both your slots.
Click to expand...
Click to collapse
How do you do this? I have a feeling I have done this also but I dont know how to go about this.
JohnsNotHome said:
How do you do this? I have a feeling I have done this also but I dont know how to go about this.
Click to expand...
Click to collapse
you do this in fastboot. Get into fastboot then connect to your computer, (make sure to get adb and fastboot installed). Then run those commands.
harpin14789 said:
you do this in fastboot. Get into fastboot then connect to your computer, (make sure to get adb and fastboot installed). Then run those commands.
Click to expand...
Click to collapse
I did run those commands once I got connected. But every time I tried to reboot it always took me back to the fast boot screen.
Once I flashed twrp before installing the Android 10zip I tried switching the slots on twrp. That also didn't do anything.
So now I have 2 worries. Did I wipe out my original Android 10? Is it still sitting there somewhere? Have I messed up anything by switching the slots? Should I have performed a reformat after getting back TWRP? I'm kinda worried, hope you can help.
Main thing is I have it working now but I wanna make sure I've learned my lesson. Thank you.
JohnsNotHome said:
I did run those commands once I got connected. But every time I tried to reboot it always took me back to the fast boot screen.
Once I flashed twrp before installing the Android 10zip I tried switching the slots on twrp. That also didn't do anything.
So now I have 2 worries. Did I wipe out my original Android 10? Is it still sitting there somewhere? Have I messed up anything by switching the slots? Should I have performed a reformat after getting back TWRP? I'm kinda worried, hope you can help.
Main thing is I have it working now but I wanna make sure I've learned my lesson. Thank you.
Click to expand...
Click to collapse
ok, you need to flash a fastboot rom. Download it and run the flashall-fastboot.bat, try without wiping data first (it will ask if you want to format userdata). If that still doesn't fix it, then you try again with userdata wiped.
If that doesn't work. you need to use msm download to fully recover (this will fully wipe and recover your phone to pie) back to locked bootloader.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
harpin14789 said:
ok, you need to flash a fastboot rom. Download it and run the flashall-fastboot.bat, try without wiping data first (it will ask if you want to format userdata). If that still doesn't fix it, then you try again with userdata wiped.
If that doesn't work. you need to use msm download to fully recover (this will fully wipe and recover your phone to pie) back to locked bootloader.
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thank you for this. I will save this piece of information for the future.
But like I said. Everything is working fine now. I was worried that it hadn't wiped out all my data and the OS and everything else was just sitting there on the other slot. Now I understand that it is technically not possible.
My other worry is that it was not wiped out properly and that it could cause problems and bugs when using the device. And lastly that it would cause problems when future updates come (in regards to the slots thing). I'm a bit of a worrier.. sorry about this.
JohnsNotHome said:
I did run those commands once I got connected. But every time I tried to reboot it always took me back to the fast boot screen.
Once I flashed twrp before installing the Android 10zip I tried switching the slots on twrp. That also didn't do anything.
So now I have 2 worries. Did I wipe out my original Android 10? Is it still sitting there somewhere? Have I messed up anything by switching the slots? Should I have performed a reformat after getting back TWRP? I'm kinda worried, hope you can help.
Main thing is I have it working now but I wanna make sure I've learned my lesson. Thank you.
Click to expand...
Click to collapse
This post was confusing, as it makes it sounds like you were stuck not being able to boot, just stuck going to fastboot screen. Then at the end, you say it works, but don't explain how you eventually got it to work.
---------- Post added at 08:58 AM ---------- Previous post was at 08:53 AM ----------
JohnsNotHome said:
But like I said. Everything is working fine now. I was worried that it hadn't wiped out all my data and the OS and everything else was just sitting there on the other slot. Now I understand that it is technically not possible.
My other worry is that it was not wiped out properly and that it could cause problems and bugs when using the device. And lastly that it would cause problems when future updates come (in regards to the slots thing). I'm a bit of a worrier.. sorry about this.
Click to expand...
Click to collapse
My understanding, user data isn't duplicated Slot A/B, only the system (ROM/OS) is duplicated.
I don't think system partition would mess up anything, even it if was the old OS version. Since your device works properly now, the active system slot is obviously okay. When you get the next update, it will flash to the inactive slot, and overwrite whatever is there. Then when you reboot, that slot will switch to active.
redpoint73 said:
This post was confusing, as it makes it sounds like you were stuck not being able to boot, just stuck going to fastboot screen. Then at the end, you say it works, but don't explain how you eventually got it to work.
---------- Post added at 08:58 AM ---------- Previous post was at 08:53 AM ----------
My understanding, user data isn't duplicated Slot A/B, only the system (ROM/OS) is duplicated.
I don't think system partition would mess up anything, even it if was the old OS version. Since your device works properly now, the active system slot is obviously okay. When you get the next update, it will flash to the inactive slot, and overwrite whatever is there. Then when you reboot, that slot will switch to active.
Click to expand...
Click to collapse
Thank you so much for this. I'm sorry I was a bit confusing. My goal was to make it simple and not long but with enough info to get some help. So yeah I'm sorry (and English is my first language).
Related
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
can i RUU or something?
wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
wdkingery said:
was flashing a rom, then a kernel.. it stopped, so i rebooted. things were fine.
tried to factory reset, flash rom.. damn thing froze again. so i rebooted.
now it bootloops. i have since fastboot flashed the boot.img from the rom, and fastboot flashed the twrp.img recovery.
can get to bootloader, can get to fastboot usb, but cannot get to recovery or back to a running phone.. bootloops
please help
Click to expand...
Click to collapse
Can you relock the bootloader? If can then download the official RUU(here is 2.20 firmware http://www.htc.com/us/support/htc-one-x-att/software-updates) and that'll probably save your phone.
oh, you can use the all in one toolkit(http://forum.xda-developers.com/showthread.php?t=1952426) to relock your bootloader if you can.. good luck
TheEmpyre said:
So I have noticed with my phone (hboot 1.14) I have to DISCONNECT it from my computer while in bootloader to be able to boot into recovery. So I do the following:
With phone in bootloader fastboot mode:
1) fastboot reboot-bootloader
2) While the screen is black, DISCONNECT the cable
3) In bootloader, use vol keys navigate to Recovery
4) Hopefully profit
Give it a try
Click to expand...
Click to collapse
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing. tried to mount SD card: windows wants to format it. **** me
wdkingery said:
GOD ALMIGHTY what in the gayness.
thanks dude. was the problem.
now i have a probably bigger problem; unable to mount SD card.. i think i have read that means a bad thing
Click to expand...
Click to collapse
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
iElvis said:
You probably corrupted it at some point in this process. You need to mount with your pc and reformat. It happens.
Click to expand...
Click to collapse
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
wdkingery said:
you are saying if i allow windows to format it, i won't have a brick, but instead will be able to fix my problem?
Click to expand...
Click to collapse
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
TheEmpyre said:
Sweet! Glad I could help, it took me a while to figure it out too, my palms were all sweaty thinking I derped my phone. And about the un-mountable SD card:
I had the same problem with my Nexus 10 when I was unlocking the bootloader, and all I had to do was actually do a format via Recovery (TWRP). Then I was able to boot into the ROM -- although I wasn't able to mount the Nexus 10 SD card still....so thats still a mystery. But I was able to get into the installed ROM
Click to expand...
Click to collapse
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
wdkingery said:
i tried that, and it failed.
i almost had windows format it, but i don't know which format type (FAT 32?)
and i'm still not clear if it will brick if i do
NEW EDIT: it doesn't brick, use default format type.
looks like i'm out of the weeds, thanks for all the quick replies.
Click to expand...
Click to collapse
Does your TWRP not have a "Format Data" Option in the Wipe Menu?
Edit: Just read your most recent edit, happy flashing hope everything works out. Oh and add [Solved] to your title if you don't mind
it does, but even that didn't work..
Hello all
I have a baaaaad situation going on!
I have been trying to delete me superuser in twrp, but something terrible happened....
1) When i boot my 1+ it just stays black.
2) When i boot into fastboot it just shows a linux penguin logo and noting else.
3) When i go to twrp i can do multiple things like adb sideload, and i can push a rom to my phone.
-> but everytime i do this and try to install it, it just fails and says i have no OS installed when i want to reboot.
I've contacted support from 1+ but nothing yet so far...
Anyone here who can help me? (i'm open for teamviewer and even want to pay the person who can fix my Oneplus)
Hoping one of you can help me!
Greetz
Michel
(I have a picture of the logo but i can't post i due to beiing a new member here )
You can't communicate with your phone through fastboot and ADB? Oh ****...
How did you manage to replace the bootloader with a Linux penguin? When you go into fast boot and type does fast boot devices does the pc recognize the phone?
Sent from my One A0001 using Tapatalk
The thing is, i was rooting my device and after i've done that my rootchecker told me the root was incomplete...
So smart as i was i started a complete unroot, to do it all over again...
In this process my device got stuck... so i booted in TWRP recovery to uninstall everything from the root over there..
Here i managed to delete my complete OS.... 8-|
After reading every tutorial and guide i figured out that on my phone my developper otions were NOT enabled...
So i contacted the oneplus support, who even remotely connected to my computer from Beijing to Belgium.. but never the less my problem was not solved and i was still stuck on the f*cking Linux logo...
So i started searching for a flashable ROM (in this case i found Pacman Nightly Signed) to flash on my phone through command on Windows.
After many hours and even more attempts i managed to go in adb en flash it by the sideload way.
So not through "adb push romname.zip /sdcard...." but by "adb sideload romname.zip /sdcard...."
And the pacman rom started to install and booted my phone to language selection...
PS: i cried :cyclops:
Glad to hear that you fixed your phone. I wouldn't contact oneplus support for things like this, chances are you'll get a reply back from xda faster as well as searching on your own to resolve the issue.
Sent from my One A0001 using Tapatalk
OnePlus One no OS, no Charge and that stupid lunix penguin
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement
Ashleigh.17 said:
:crying:So basically I have the same issue, I tried to install Oxygen OS and managed to remove my Entire operating system and format my entire sdcard so I've managed to push a few possible ROMs to my device and they won't install and it won't let me install any mof them and now I've lost the charge on my device.
Please tell me theirs something I can do to fix this.:crying:
Click to expand...
Click to collapse
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon
timmaaa said:
More info required. What recovery do you have installed? Exactly what error are you getting when flashing the ROMs? You probably just need to flash the right firmware first.
Transmitted via Bacon
Click to expand...
Click to collapse
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
---------- Post added at 10:09 AM ---------- Previous post was at 09:58 AM ----------
Coug76 said:
Fast boot flash a TWRP image. Flash CM12 nightly via OTG. You will be good from there.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I'm having an issue gettjngit into fastboot its died and all I'm getting is a black flashing screen!
Any tips on how to get it to charge?
Ashleigh.17 said:
I'm using TWRP
When I did manage to push some files to the device and tried to install them it failed instantly. I tried Cyan Hacker V2 the new Oxygen os and cm-11 and one of my backups, but all of them had the same issue. I can only vaguely remember the command which I think said 'partitions updating' then under the completed tab at the top of the screen in Red text it said failed.
This isn't my main concern anymore the device has died and won't charge so I can't get it to boot into fast boot or Recovery all its done when connected to the charger is light up with a black screen, vibrate then turn off, it repetats that a couple of times then it goes off again and no life at all, if I leave it of the charger for bit and try plugging it in again I get the same flashing black screen but again no charge.
Click to expand...
Click to collapse
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon
timmaaa said:
Yep, it's almost definitely a case of not having flashed the right firmware after coming from Oxygen. Leave it plugged in for eight hours, don't touch it in that time, then try to power it on again.
Transmitted via Bacon
Click to expand...
Click to collapse
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?
Ashleigh.17 said:
Okay I'll leave it through the day. After I get it to charge how will I get an OS onto it and how will I ensure that its got the right firmware? And if it all goes caput is this a valid reason for a renewed device from oneplus?
Click to expand...
Click to collapse
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon
timmaaa said:
If you want to flash a Lollipop ROM the best way is to first perform a full wipe (system, data, cache, dalvik cache) in TWRP, then flash this firmware:
https://docs.google.com/file/d/0B98G0KTJwnBFdVgxZ0x5RzNJSE0/edit?usp=docslist_api
Then flash this modem:
https://docs.google.com/file/d/0B98G0KTJwnBFU0Z1TUIyVE50WW8/edit?usp=docslist_api
Then go to the reboot menu and reboot back to recovery. Then flash whatever Lollipop ROM you want to use, and reboot your phone. If you still have no success after doing that then you'll need to try to flash the stock images with fastboot, I have a download and instructions in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
If that gets your phone booting then you can go ahead and try the above steps again to flash a Lollipop ROM.
No, this wouldn't be covered by warranty. Unlocking the bootloader and rooting this device doesn't void the warranty but they've stated that if you brick the phone while flashing (or the like) then it isn't covered. This is a case of user error, you didn't ensure that you had the correct firmware before flashing.
Transmitted via Bacon
Click to expand...
Click to collapse
okay
thank you for all your help hopefully I'll be posting later with some good news
So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?
Ashleigh.17 said:
So I have gained access to the device in both TRWP and fastboot mode but I have encountered more problems,
Theirs is no OS, but their is a recovery the logical thing here would be boot it in fast boot and push files to the device and install those using the recovery easy right!!
no the boot loader is locked and so I can't flash anything I've downloaded about 2 or 3 tools kits to get it unlocked, when I use them the device reboots but wont load into fastboot, I can get it to with some tampering it doesn't have an exact method
any ideas guys?
Click to expand...
Click to collapse
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
timmaaa said:
Why did you lock your bootloader? You need to go here:
http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
Flash that through TWRP and your bootloader will be unlocked again.
PS. You can't push files to the device in fastboot mode, only adb can push files and adb doesn't work in fastboot mode. Once you've unlocked your bootloader again you'll need to flash the stock images with fastboot. Download and instructions are in section 8 of my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
Click to expand...
Click to collapse
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much
Ashleigh.17 said:
You HERO!!!!!!!!!!!!!!!!!!!
I actually love you right now thank you so much
Click to expand...
Click to collapse
Lol, no worries, glad to help.
timmaaa said:
Lol, no worries, glad to help.
Click to expand...
Click to collapse
This is better than the best soapserie
....
Is he going to make it?
Yes
Great! :good:
Oooooh nooooo!!!
He's got a locked bootloader
Damn F*ING
This will never turn out right
OH, look here comes @timmaaa again
He says what? :silly:Really is it possible
Yes YES YYEEEEESSS
I did it, it's working again
I loooove you
:highfive::highfive::highfive:
I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??
ElmoRapz said:
I have similar issues at the moment. I tried to flash over Oxygen OS and it kept failing. Upon factory wiping the current OS to put CM 12 Nightly, I accidentally deleted all of my data. Now 54,xxx MB is on my phone, meaning it wiped all internal memory, the system is only 20MB and data is 6MB. I tried to plug in my phone to fast boot mode, and my computer wouldn't read it. I did all I could to maybe get it to read, and not a single thing popped up. I do not believe my bootloader is locked, but there could be a possibility that it could. Any suggestions to get an OS pushed over through ADB or Fastboot??
Click to expand...
Click to collapse
It looks like you did the same thing that I did.
Its a pretty easy fix your going to be able to avoid all of the unlocking boot loader issues I had.
To begin with when your try an turn the device on is the screen flashing black?
OK since we have multi partitions, if we mess up on a flash or want to just test things can we switch to from a to b or vise versa and it will boot whatever was on that partition or does it not work that way?
Bradl79 said:
OK since we have multi partitions, if we mess up on a flash or want to just test things can we switch to from a to b or vise versa and it will boot whatever was on that partition or does it not work that way?
Click to expand...
Click to collapse
I'm interested in this, as well. Also, I just came from the 3t. Love your rom.
As far as I could tell from trial and error that is the way it is supposed to work, but I am having issues on one of both Partitions getting locked after deleting magisk but it working again after flashing magisk again, so I guess I did something wrong somewhere in the beginning when clean flashing to start over again
You cant brick your phone with flashing
So try whatever you want, you can always restory your phone.
matze19999 said:
You cant brick your phone with flashing
So try whatever you want, you can always restory your phone.
Click to expand...
Click to collapse
That's for sure, but do you happen to know how to get 2 working Partitions, the way it should be? Because now I only have one and the other goes straight to TWRP.
Essentially you should have 2 identical (working) OOS'es running till you screw the active one up but I can't get it like that. I used to have it but then I didn't understand he A/B yet so I didn't even knew
SaGaR_ said:
That's for sure, but do you happen to know how to get 2 working Partitions, the way it should be? Because now I only have one and the other goes straight to TWRP.
Essentially you should have 2 identical (working) OOS'es running till you screw the active one up but I can't get it like that. I used to have it but then I didn't understand he A/B yet so I didn't even knew
Click to expand...
Click to collapse
You have the system.img of your os, right?
Flash it to both slots using
fastboot flash system_a system.img
and
fastboot flash system_a system.img
Now just boot into your system and set it up.
Now, when your system gets an update, it will be straight installed to the other slot and when you reboot your phone the next time, it will simply just boot to the other slot. No flashing or something else.
When the slot change didn't work probably, the phone will boot to the last used slot and you have to install the update again.
I hope I was able to help you
matze19999 said:
You cant brick your phone with flashing
Click to expand...
Click to collapse
Well... could really get tricky without a PC and/or debugging activated . Just saying.
matze19999 said:
You have the system.img of your os, right?
Flash it to both slots using
fastboot flash system_a system.img
and
fastboot flash system_a system.img
Now just boot into your system and set it up.
Now, when your system gets an update, it will be straight installed to the other slot and when you reboot your phone the next time, it will simply just boot to the other slot. No flashing or something else.
When the slot change didn't work probably, the phone will boot to the last used slot and you have to install the update again.
I hope I was able to help you
Click to expand...
Click to collapse
Thank you, I thought so, I tried to achieve that from TWRP but that gave some weird "internal error" message on one Partition while everything worked fine it didn't gave a clean/fresh install feeling.
But I only have the zip files no .IMG files
MickyFoley said:
Well... could really get tricky without a PC and/or debugging activated . Just saying.
Click to expand...
Click to collapse
USB debugging doesn't care. But you need always a Pc
---------- Post added at 08:57 AM ---------- Previous post was at 08:57 AM ----------
SaGaR_ said:
Thank you, I thought so, I tried to achieve that from TWRP but that gave some weird "internal error" message on one Partition while everything worked fine it didn't gave a clean/fresh install feeling.
But I only have the zip files no .IMG files
Click to expand...
Click to collapse
What is inside the zip file? A payload.bin or a system.img?
matze19999 said:
USB debugging doesn't care. But you need always a Pc
Click to expand...
Click to collapse
Why do you always need a PC? I have done only the boot of TWRP with PC and from there everything from the phone.
Btw,I don't know if I'm the only one, but when I connect my phone to PC with the USB it doesn't recognize it until I turn of USB debugging. But I know that the problem is with my windows 10. Because on other PC's it works no problem and previous phones always worked without issues
matze19999 said:
What is inside the zip file? A payload.bin or a system.img?
Click to expand...
Click to collapse
Payload.bin
SaGaR_ said:
Why do you always need a PC? I have done only the boot of TWRP with PC and from there everything from the phone.
Btw,I don't know if I'm the only one, but when I connect my phone to PC with the USB it doesn't recognize it until I turn of USB debugging. But I know that the problem is with my windows 10. Because on other PC's it works no problem and previous phones always worked without issues
Payload.bin
Click to expand...
Click to collapse
Not always... But when your system and even recovery won't boot anymore, you have to use the msmdownloadtool to restore your system. Without a Pc, you can throw your phone into the trash ?
You can extract the payload.bin with a small Linux script
https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15
matze19999 said:
Not always... But when your system and even recovery won't boot anymore, you have to use the msmdownloadtool to restore your system. Without a Pc, you can throw your phone into the trash ?
Click to expand...
Click to collapse
True, but you could always boot to bootloader and fastboot TWRP or something like that.
And what's this MSMDownloadTool ?
matze19999 said:
You can extract the payload.bin with a small Linux script
https://gist.github.com/ius/42bd02a5df2226633a342ab7a9c60f15
Click to expand...
Click to collapse
But why would I need to extract Payload.bin?
SaGaR_ said:
True, but you could always boot to bootloader and fastboot TWRP or something like that.
And what's this MSMDownloadTool ?
But why would I need to extract Payload.bin?
Click to expand...
Click to collapse
No, you can't always boot to .bootloader / fastboot.
In this case, you need the msmdownloadtool. It writes all partitions again to your phone.
SaGaR_ said:
True, but you could always boot to bootloader and fastboot TWRP or something like that.
And what's this MSMDownloadTool ?
But why would I need to extract Payload.bin?
Click to expand...
Click to collapse
My OP6 wouldn't boot, just went to a black screen and kept flashing a blue notification light. I fastboot the twrp.img and all my files were present on internal storage. I did a restore, flashed twrp installer and Magisk and was back in business.
If you can fastboot your good if not thats when you need the msmdownloadtool
It really can get tricky. Flashing an OTA zip overwrites recovery because recovery is part of the boot img. So always flash the twrp installer then magisk after you flash an OTA rom. Also, there is a /backup partition survives a flash (usually) so I will stick stuff there temporarily to keep me from having to whip out my PC if stuff goes south. I used it when I tried out Android P lol
MickyFoley said:
Well... could really get tricky without a PC and/or debugging activated . Just saying.
Click to expand...
Click to collapse
matze19999 said:
You cant brick your phone with flashing
So try whatever you want, you can always restory your phone.
Click to expand...
Click to collapse
What happens if you dd to zero all bootloader partitions? It can still be restored with que qualcomm protocol to connect to PC?
RusherDude said:
What happens if you dd to zero all bootloader partitions? It can still be restored with que qualcomm protocol to connect to PC?
Click to expand...
Click to collapse
Yeah, ofc, because the low level bootloader is read only and you can't overwrite it
matze19999 said:
Yeah, ofc, because the low level bootloader is read only and you can't overwrite it
Click to expand...
Click to collapse
But the read only bootloader runs the Qualcomm protocol to connect it to PC or fasboot? otherwise how do you flash the other partitions?
RusherDude said:
But the read only bootloader runs the Qualcomm protocol to connect it to PC or fasboot? otherwise how do you flash the other partitions?
Click to expand...
Click to collapse
Turn your device off, hold the louder volume button and connect the phone to your PC. Now you're in Qualcomm low level bootloader. Start the msmdownloadtool and press the flash button
matze19999 said:
Turn your device off, hold the louder volume button and connect the phone to your PC. Now you're in Qualcomm low level bootloader. Start the msmdownloadtool and press the flash button
Click to expand...
Click to collapse
That doesn't answer my question! Do you mean that, AFTER wiping the bootloader partitions, that can still be done? aka in the read-only memory bootloader is the qualcoom protocol function?
I mean, even if that happens from the phone turned off, it can be the first bootloader partition that gets wiped the one that does the qualcomm protocol stuff. I wanna know if its the read only the one that has the qualcomm protocol
So, I want to say that my Nokia 8 TA-1004 is having Bootloop. This happens very occasionally and randomly. It just attacks unexpected. I can't see what is the problem or what's the source of it. Thankfully, I have the logcat file. However, I do not understand what was the main cause. So please, I am asking the experts in here to help me identify the source of this error.
The Bootloop just boot like 4-5 times and then stopped Bootloop or sometimes just go straight to DOWNLOAD MODE and I had to restart manually. After that, i was able to gointo system like exploring like usual, and then it happens again. Sometimes not opening the app also happens. Repeat until you gets the nerve.
The phones status is rooted with magisk and unlocked bootloader but no twrp yet. Also, I am at 4.88B SP01 June,01 patch. If you are telling me that the root is the cause, then it is unlikely since it has been weeks since I had it rooted but the problem just came these recently.
Once again, I ask for the help of forumers here. I want to at least enjoy my phone that I love. I dont really want to sell the phone anymore.
Here's the link of logcat:
https://www16.zippyshare.com/v/2W0SVK8t/file.html
I promise. No viruses. Thank you
Hey, I suspect that this problem could be fixed by flashing original bootloader image.
I assume you have flashed an unsuitable image and I think you are using an unlocked bootloader, that's why you are facing this problem.
error748 said:
Hey, I suspect that this problem could be fixed by flashing original bootloader image.
I assume you have flashed an unsuitable image and I think you are using an unlocked bootloader, that's why you are facing this problem.
Click to expand...
Click to collapse
Do you mean flashing original Boot.img? As we know, to gain root, we need to flash patched boot.img with magisk. Do you mean this kind of issue? I notice the problem is in Android System. It says failed to load as data may corrupt. Google is also not responding and Google play services.
Unlocked Bootloader isnt the issue. But, I do think image is unsuitable. However, I have patched boot.img as the same as the version of Nokia. Is such thing still happen?
godofknife said:
Do you mean flashing original Boot.img? As we know, to gain root, we need to flash patched boot.img with magisk. Do you mean this kind of issue? I notice the problem is in Android System. It says failed to load as data may corrupt. Google is also not responding and Google play services.
Unlocked Bootloader isnt the issue. But, I do think image is unsuitable. However, I have patched boot.img as the same as the version of Nokia. Is such thing still happen?
Click to expand...
Click to collapse
now do one thing. flash stock boot img (will break wifi), after that download official twrp and boot into it. then from twrp flash twrp zip file provided with official boot img. reboot to twrp and flash latest magisk beta. (you will have wifi working after this)
This way you will get root and stable system.. no need to flash patched boot img anymore..
Make sure to revert back to stock boot first before flashing twrp..
sumitinhome said:
now do one thing. flash stock boot img (will break wifi), after that download official twrp and boot into it. then from twrp flash twrp zip file provided with official boot img. reboot to twrp and flash latest magisk beta. (you will have wifi working after this)
This way you will get root and stable system.. no need to flash patched boot img anymore..
Make sure to revert back to stock boot first before flashing twrp..
Click to expand...
Click to collapse
sumitinhome, I just did factory reset. The problem STILL HAPPENS. It means it wasn't any of the app but from the system or the boot.img itself perhaps.
With no way to enter the system, how do i get into the fastboot now? By pressing volume down + Power (That shows DOWNLOAD MODE)? Is that the fastboot? Then yet again, the only issue that I have is the exactly driver for Nokia 8. I found lots of drivers in the internet but I am quite confused which one is the real driver of Nokia 8 to be able to detect in fastboot and ADB. Do you have a driver installer?
Assuming if you will have given Nokia driver and I managed to get into fastboot mode by using hard key, do I type this command?
fastboot flash boot.img? Or is it wrong command?
Thank you and sorry if i ask too many questions.
godofknife said:
sumitinhome, I just did factory reset. The problem STILL HAPPENS. It means it wasn't any of the app but from the system or the boot.img itself perhaps.
With no way to enter the system, how do i get into the fastboot now? By pressing volume down + Power (That shows DOWNLOAD MODE)? Is that the fastboot? Then yet again, the only issue that I have is the exactly driver for Nokia 8. I found lots of drivers in the internet but I am quite confused which one is the real driver of Nokia 8 to be able to detect in fastboot and ADB. Do you have a driver installer?
Assuming if you will have given Nokia driver and I managed to get into fastboot mode by using hard key, do I type this command?
fastboot flash boot.img? Or is it wrong command?
Thank you and sorry if i ask too many questions.
Click to expand...
Click to collapse
1. download mode is fastboot mode.. no difference there.
2. unfortunately i dont have installer for drivers but you can find it if you browse nokia section in this forum.
3. you will need command 'fastboot flash boot_a boot.img' and 'fastboot flash boot_b boot.img' to flash stock boot img to your phone..
4. if you wish to install twrp then you will need to follow instructions from following thread
https://forum.xda-developers.com/nokia-8/development/official-twrp-nb1-t3832232
Make sure to read the thread and comments carefully before doing anything.
Hope it helped.
sumitinhome said:
1. download mode is fastboot mode.. no difference there.
2. unfortunately i dont have installer for drivers but you can find it if you browse nokia section in this forum.
3. you will need command 'fastboot flash boot_a boot.img' and 'fastboot flash boot_b boot.img' to flash stock boot img to your phone..
4. if you wish to install twrp then you will need to follow instructions from following thread
https://forum.xda-developers.com/nokia-8/development/official-twrp-nb1-t3832232
Make sure to read the thread and comments carefully before doing anything.
Hope it helped.
Click to expand...
Click to collapse
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
godofknife said:
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
Click to expand...
Click to collapse
I have it. Wait sometime.. i will upload it on gdrive and share you link
sumitinhome said:
I have it. Wait sometime.. i will upload it on gdrive and share you link
Click to expand...
Click to collapse
Yes sumitinhome, thank you so much. Try make it one upload with the driver. All that and I will do the fastboot command asap..
Oh yeah, one verify question. When the bootloader is unlocked, updating the newest ROM after august will lock the bootloader again or not? Some say yes, some say no. A member name hikari stated no, we are unaffected. But, some say relock again. Which is true?
godofknife said:
Yes sumitinhome, thank you so much. Try make it one upload with the driver. All that and I will do the fastboot command asap..
Oh yeah, one verify question. When the bootloader is unlocked, updating the newest ROM after august will lock the bootloader again or not? Some say yes, some say no. A member name hikari stated no, we are unaffected. But, some say relock again. Which is true?
Click to expand...
Click to collapse
we are unaffected.. and i have only boot img unfortunately.. i dont have drivers..
and dont update to august yet.. let pie come and update to pie directly then..
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
godofknife said:
Hey there, thanks for the fast respond. It greatly helps.
Alright, I am waiting for the driver. Also, I checked anywhere in the forum section of Nokia 8 but none of them have 00WW_4.88bSP01 version of stock boot.img which is 1st June 2018 patch.
Do you happen to have had it? Is it okay if i ask for it? Thank you.
Click to expand...
Click to collapse
here is boot img
https://drive.google.com/file/d/1XtxIWQdn9dbtt1tJydM_6fFhslRZfozr/view?usp=drivesdk
sumitinhome said:
we are unaffected.. and i have only boot img unfortunately.. i dont have drivers..
and dont update to august yet.. let pie come and update to pie directly then..
---------- Post added at 02:10 PM ---------- Previous post was at 02:04 PM ----------
here is boot img
https://drive.google.com/file/d/1XtxIWQdn9dbtt1tJydM_6fFhslRZfozr/view?usp=drivesdk
Click to expand...
Click to collapse
Ah ha, thank you very much. I just need one more requirement. The driver. Honestly, there are so many drivers for Nokia 8 and none of them seems to work with my device detection. There's also type F, M driver..... Seriously confusing.
@sumitinhome, you are awesome. I must say thank you for helping me. Phone is no longer in bootloop state. However, I may require just little more help. I have also installed TWRP and succeeded. The problem is that the WIFI breaks. I went ahead and installed Magisk using zip one like you mentioned the steps in installing TWRP. It still doesn't solve the WIFI problem. How could this be? (Do note that I did not use fastboot flash twrp.img. I use fastboot boot twrp.img instead)
I also have other questions. During MTP in TWRP, I saw the partition drive; The internal storage and USB-OTG as given in picture below. What is the second drive meaning?
Second question is why is Magisk manager only showing Installed version v17.1? And the button is just uninstalled. I recall there are other buttons and feature like Safety Net and advance settings.
Finally, I want to know how do we get into recovery mode without using ADB command everytime? I tried pressing Volume UP + Power. But, it didn't go into TWRP. It just goes normal reboot.
Thank you so much once again.
Pic: https://ibb.co/jFtHPp
godofknife said:
@sumitinhome, you are awesome. I must say thank you for helping me. Phone is no longer in bootloop state. However, I may require just little more help. I have also installed TWRP and succeeded. The problem is that the WIFI breaks. I went ahead and installed Magisk using zip one like you mentioned the steps in installing TWRP. It still doesn't solve the WIFI problem. How could this be? (Do note that I did not use fastboot flash twrp.img. I use fastboot boot twrp.img instead)
I also have other questions. During MTP in TWRP, I saw the partition drive; The internal storage and USB-OTG as given in picture below. What is the second drive meaning?
Second question is why is Magisk manager only showing Installed version v17.1? And the button is just uninstalled. I recall there are other buttons and feature like Safety Net and advance settings.
Finally, I want to know how do we get into recovery mode without using ADB command everytime? I tried pressing Volume UP + Power. But, it didn't go into TWRP. It just goes normal reboot.
Thank you so much once again.
Pic: https://ibb.co/jFtHPp
Click to expand...
Click to collapse
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button.
This will get back wifi. after that you can update to latest august patch too if you want and then flash twrp.
And about that OTG thing, don't worry twrp is being updated it will be fixed very soon. People are working on it.
sumitinhome said:
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button.
This will get back wifi. after that you can update to latest august patch too if you want and then flash twrp.
And about that OTG thing, don't worry twrp is being updated it will be fixed very soon. People are working on it.
Click to expand...
Click to collapse
I see. Number 3 has Encryption. Also, before i can do this, i have a new problem. I was so stupid. I accidentally format everything including the system which leaves me NO OS. I should have just wipe data (factory reset). Not advanced wipe. Can I still install Stock rom (any version) with twrp? What do i do?
@sumitinhome, also I forgot to mention. SD Card and Internal storage is not detected in TWRP Mode. I checked in my PC. ADB Sideload is also fail. Is this the end of my phone fate?
EDITED: Never mind. I was using the obsolete TWRP Version. I updated to the latest one and SD Card and internal is detected in TWRP once again.
godofknife said:
@sumitinhome, also I forgot to mention. SD Card and Internal storage is not detected in TWRP Mode. I checked in my PC. ADB Sideload is also fail. Is this the end of my phone fate?
EDITED: Never mind. I was using the obsolete TWRP Version. I updated to the latest one and SD Card and internal is detected in TWRP once again.
Click to expand...
Click to collapse
well done
sumitinhome said:
well done
Click to expand...
Click to collapse
Thank you.
godofknife said:
I see. Number 3 has Encryption. Also, before i can do this, i have a new problem. I was so stupid. I accidentally format everything including the system which leaves me NO OS. I should have just wipe data (factory reset). Not advanced wipe. Can I still install Stock rom (any version) with twrp? What do i do?
Click to expand...
Click to collapse
@sumitinhome, how about this? I still have the issue. NO OS is running.
godofknife said:
Thank you.
@sumitinhome, how about this? I still have the issue. NO OS is running.
Click to expand...
Click to collapse
told you flash stock boot img again.. and use the above method i mention to flash firmware..
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button
sumitinhome said:
told you flash stock boot img again.. and use the above method i mention to flash firmware..
Do one thing.
Flash stock boot img again. and after that do the following
1) Full charge your phone.
2) Get a MicroSD card ( 8 or 16 GB )
3) Download this - https://mega.nz/#!mRZHDaJI!3KrT2F0ZE...KQux5EvPWVGI_4
4) Copy it to SDCARD from your PC.
5) Put the SD card in ur mobile.
6) Go to recovery
7) Select update, from SDCARD - start flashing by pressing power button
Click to expand...
Click to collapse
That was also the solution for NO OS? Wow. Thanks. Um, the download link need Decryption key. Do you happen to have it?
godofknife said:
That was also the solution for NO OS? Wow. Thanks. Um, the download link need Decryption key. Do you happen to have it?
Click to expand...
Click to collapse
no it doesn't need any key
I was downloading a OTA update the other day & in preparation I thought I would go ahead & uninstall Magisk. Magisk asked me if I wanted to restore images or uninstall I just uninstalled, not ever having made a image before I didn't know what it was talking about.
The phone rebooted once then booted again into TWRP, I can't get back into my phones OS.
Later I couldn't get back into TWRP so I had to boot using the fastboot commands in Windows. I was able to see & "Backup" the contents of my phone to an external drive.
Now how do I get back into my phone like normal?
Do I need to flash an image or I've seen other threads they wipe the data & there phone boots?
Please advise.
Thank you
justinstrack said:
I was downloading a OTA update the other day & in preparation I thought I would go ahead & uninstall Magisk. Magisk asked me if I wanted to restore images or uninstall I just uninstalled, not ever having made a image before I didn't know what it was talking about.
The phone rebooted once then booted again into TWRP, I can't get back into my phones OS.
Later I couldn't get back into TWRP so I had to boot using the fastboot commands in Windows. I was able to see & "Backup" the contents of my phone to an external drive.
Now how do I get back into my phone like normal?
Do I need to flash an image or I've seen other threads they wipe the data & there phone boots?
Please advise.
Thank you
Click to expand...
Click to collapse
First of all, no need to uninstall Magisk - unnecessary and waste of time.
Once in TWRP (fastboot boot twrp.img, or via your phone if you still can) - flash OOS OTA update (as that was what you were trying to do).
Then flash TWRP, reboot TWRP. Now you can flash Magisk again (so you get root, since you removed it for some reason).
Everything should be fine.
only4dank said:
First of all, no need to uninstall Magisk - unnecessary and waste of time.
Once in TWRP (fastboot boot twrp.img, or via your phone if you still can) - flash OOS OTA update (as that was what you were trying to do).
Then flash TWRP, reboot TWRP. Now you can flash Magisk again (so you get root, since you removed it for some reason).
Everything should be fine.
Click to expand...
Click to collapse
Unfortunately now I can't get the "fastboot boot twrp.img" to boot into twrp? FAILED authentication.
Now what?
Fastboot devices work & the reboot function works, just can't boot twrp.img. I've seen somewhere I can maybe force boot the device idk if it will work. damn
justinstrack said:
Unfortunately now I can't get the "fastboot boot twrp.img" to boot into twrp? FAILED authentication.
Now what?
Fastboot devices work & the reboot function works, just can't boot twrp.img. I've seen somewhere I can maybe force boot the device idk if it will work. damn
Click to expand...
Click to collapse
Sorry to hear. You are going to have to provide logs of what commands you are typing into terminal, and what is the output.
So are you in TWRP or not. I literally have no idea what is going on with your device or what you are doing.
Next time, maybe check guides in this forum of how to do what you are doing.
Randomly uninstalling/installing/flashing/issuing commands via terminal/random backup and restores/etc.... does not sit well with android devices.
I'll try another pc tonight.
If you can get back to twrp you need to flash magik to boot normally
Still can't back into twrp. Failedremote: failed to load/authenicate boot image: Load error.)
Tried a different computer. Tried deleting my fastboot files on PC then copying them from a backup thinking I modified the twrp image wrong thinking this unmotified version would work, still nothing.
Can I get some advice links to guides. Thank you.
justinstrack said:
Still can't back into twrp. Failedremote: failed to load/authenicate boot image: Load error.)
Tried a different computer. Tried deleting my fastboot files on PC then copying them from a backup thinking I modified the twrp image wrong thinking this unmotified version would work, still nothing.
Can I get some advice links to guides. Thank you.
Click to expand...
Click to collapse
Still.... what are you typing into terminal... take a screen shot .....
ARE YOU SURE you are typing 'fastboot boot twrp.img' - BOOT, not FLASH!!!???
I'm now able to boot into twrp. Had to use fastboot --set-active=a. Worked great. Left it like that at home. I'm at work now.
What next?
justinstrack said:
I'm now able to boot into twrp. Had to use fastboot --set-active=a. Worked great. Left it like that at home. I'm at work now.
What next?
Click to expand...
Click to collapse
I would start by reading forum page 1 information about what you are trying to do.
I already explained to you the order to flash to make things work.
If that is not enough, once again, go learn what you are trying to do (via the forum thread).
You will probably save yourself these types of situations in the future if you understand what you are doing.
Good luck.
Everything is FULLY Operational Thank You. What a experience but Ive learned.
justinstrack said:
Everything is FULLY Operational Thank You. What a experience but Ive learned.
Click to expand...
Click to collapse
And not even a single thanks button hit or anything... Weird flex, but OK
I'm so sorry LOL. found it. Have a good day xda forum members, I found the button. THANK YOU