Database Users

[Q] Nexus 10 stuck in boot after attempting root

Hi.
So, a quick overview. My laptop suddenly stopped recognizing my Nexus 10 while in the midst of transferring some files over. I decided to finally root. I used the cf-autoroot tool for Nexus 10 Lollipop. The last step of the rooting involves an automatic reboot. Now my Nexus 10 is stuck in the boot.
Details:
theunlockr (DOT) com/2014/11/22/how-to-root-the-nexus-10-on-android-5-0/
That is the guide I used, including the linked cf-autoroot. Sorry for the formatting, I don't have enough posts to post links.
My Nexus 10 is stuck on the step where it shows the four circles moving around. Not sure if that's important.
The cf-autoroot appeared to work successfully except for a piece in the middle that reads:
Same problem. The procedure seemed to go well, except maybe the mounting failed? It says:
Mounting...
- System
- Cache
--- Fail
I tried using the tool several times on two computers, and did my best to update drivers directly from Google (it appears the drivers are all up to date).
My Nexus 10 was on Lollipop. As far as I know, it was up to date, so I think that means it was on 5.0.1
Help?

Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s

Khaon said:
Hello autoroot is no longer required. Supersu from recovery is enough.
You could just reflash original kernel
Does
Fastboot boot boot. Img works? It boots on the given image without flaging. The boot image is located in the archive to update
Sent from my Xiaomi MI2s
Click to expand...
Click to collapse
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.

jsgraphicart said:
This is what I have come here to find out. I'm receiving my Nexus 10 in the mail today. I'm familiar with Nexus devices so I just assume everything is the same with the Nexus 10. But I know since Lollipop came out, there have been changes to how to root on certain devices. Are you saying that everything has been fixed to where I can just install the latest TWRP and flash the latest beta SuperSU on stock ROM and I will be good? If so, then it's the same as my Nexus 5 so I shouldn't have any issues.
Click to expand...
Click to collapse
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.

Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
Thanks. I just wanted to double check before I went jumping into it. I'm looking forward to tinkering with it when I get home from work.

Khaon said:
Yep, just flash once SU through twrp(in order to get the su binary in the system partition) and then you can use play store to update the binary and the program itself.
CM12 has built in su and nighties are official now.
Click to expand...
Click to collapse
So I attempted to do all this when I got home yesterday. I found that after unlocking the bootloader, I got stuck in a boot loop. After doing some research I found that this has been an issue with the Nexus 10. Is there a reason for this? I read that locking the bootloader again fixed it, which it did. But I didn't want it locked. So I researched more and found that a a factory reset in stock recovery would fix it. I still had a boot loop. I managed to somehow get everything straightened out with a series of random tries and after installing TWRP and rooting and, again, getting the boot loop I attempted to go back into recovery but accidentally did a simple restart. For some reason, it booted right up after the restart so now I think everything is fine. But why is the Nexus 10 being so difficult? I never had these issues with other Nexus devices. Maybe some of this info will help the OP as well.

Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked

Khaon said:
Hm unlocking the bootloader does erase whole content but I guess you are already aware of that.
How long did you wait? First boot can take ages much longer than before.
I never had any issues and I have my bootloader unlocked
Click to expand...
Click to collapse
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.

nexus 10 stuck on bootload up
jsgraphicart said:
I let it sit for a while. I own a Nexus 5 and I'm familiar with the long first boot. It just seemed like a long time to me. I thought maybe since it was a two year old device that it may take longer. The device is new to me so I'm not familiar with boot times and all that are specific to it yet. But compared to the boot time after I relocked the boot loader, there was a big difference. After re-locking, it booted up in about a minute or two. Flashing TWRP even seemed to mess up some stuff. I think it may have deleted the OS or something. It couldn't mount anything afterwards and even selecting reboot boot loader gave me the prompt that there was no OS installed. So I flashed the system.img, cache.img and userdata.img manually. Which seemed to fix it. And even after I got everything straightened out, it boot up in about a minute or two again. The only time I had issues with getting it to boot is unlocking the boot loader coming from complete stock.
Click to expand...
Click to collapse
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom

tomistrouble said:
I getting the exact same thing after following instructions to root the machine
I'm not the most experience but I did my nexus 4 & 7 on 4.4.4. now on this 5.0 it seemed a lot hard this time around
I left it on boot load up screen for 3hrs and its still going round? what do I do?
Quick update: I press power +vol up + down and it comes up with the screen saving its unlocked. but the recovery mode just comes up with a android and red exclamation mark.
please help?
regards
Tom
Click to expand...
Click to collapse
Once you get in recovery mode with the android and the red explanation mark, hit all three buttons (Vol up , down and power) until (It can be tricky keep trying) you get a menu. Then use the volume buttons to select "Wipe Data/Factory rest" let it do its thing and reboot. Allow it to boot for 5-10 minutes.
Good luck

Nexus 7 bootlooping and not actually wiping partitions

My N7 has been getting laggier recently - accepting the 5.1.x OTA updates was clearly a bad idea, and possibly the 5.0.x ones. So I have been thinking of giving it a new ROM after this past weekend.
Last night, it started bootlooping, getting to the initial 'swipe to use' main screen but not accepting any touches and then crashing to a restart after a few seconds regardless.
I long ago used the Nexus Root Tool Kit to root it and install TWRP. The most recent OTA 5.1.1 update involved an update to TWRP to version 2.8.6.0. So let's install a new ROM!
I can boot into TWRP and, while there, the NRTK will also talk to the Nexus 7 over USB.
In both of them, plus a console using fastboot commands, I can wipe and format partitions. By telling TWRP to use 'rm -rf' rather than formatting, I can also get its partition repair info to think, for a while, that the partition in question is empty. But looking again reveals that it's just as full as it used to be and indeed, whether or not the formatting, flashing and installing a .zip file appears to work - including fastboot commands reporting success - no files appear to actually change on the device. NRTK will believe it has successfully installed the latest 2.8.7.0 TWRP or any ROM, but rebooting finds the old ones still there. Even all my data is there, despite repeated wipes and reformats, including to different file systems.
What can I try next? At the moment, I am just grateful that this happened before I'd tried installing a new ROM because I'm not blaming myself for all this.

lovingboth said:
What can I try next? At the moment, I am just grateful that this happened before I'd tried installing a new ROM because I'm not blaming myself for all this.
Click to expand...
Click to collapse
It's now not powering up at all. Whatever it is, it looks terminal.
Poo.

HELP: boot, system and vendor partition flashes failing!

I woke up to the OTA for the latest Android P update on my Essential phone this morning. Like a kid at Christmas, I couldn't wait. I started the OTA download and shortly after the download finished the install failed. So I tried it again thinking maybe there was a hiccup in the download, same result. Once I got home from work I figured I'd just download the fastboot image from the site and try that. Going through the steps as listed and all of a sudden random images would fail on flashing. All of the images flashed with the exception of boot, system and vendor.
What really has me worried is that the product name, bootloader version and serial number are all showing differently now afterwards.. which has me really worried that the phone is toast. I'm very careful with my devices; they aren't dropped and are always in a case with a screen protector. I'm not new to flashing roms or updates, I've been doing this for years and never had a problem.. and before someone asks, yes, flashing unlock and flashing unlock_critical was done before I started flashing the different partitions.

MRR0GERS said:
I woke up to the OTA for the latest Android P update on my Essential phone this morning. Like a kid at Christmas, I couldn't wait. I started the OTA download and shortly after the download finished the install failed. So I tried it again thinking maybe there was a hiccup in the download, same result. Once I got home from work I figured I'd just download the fastboot image from the site and try that. Going through the steps as listed and all of a sudden random images would fail on flashing. All of the images flashed with the exception of boot, system and vendor.
What really has me worried is that the product name, bootloader version and serial number are all showing differently now afterwards.. which has me really worried that the phone is toast. I'm very careful with my devices; they aren't dropped and are always in a case with a screen protector. I'm not new to flashing roms or updates, I've been doing this for years and never had a problem.. and before someone asks, yes, flashing unlock and flashing unlock_critical was done before I started flashing the different partitions.
Click to expand...
Click to collapse
Don't flash using the script. Flash them yourself with the commands from the script "fastboot flash system system.img" etc.

crixley said:
Don't flash using the script. Flash them yourself with the commands from the script "fastboot flash system system.img" etc.
Click to expand...
Click to collapse
That's what I did. I've never liked or trusted the scripts from those. I'm back to my Nexus 6 for now till I can hopefully fix the Essential.

Actually I've met this things yesterday when I was trying to flash the DP 3 for my phone. At the first time I stucked when flash the system image and I restarted to bootloader, after reboot I saw a strange serial number doesn't start with PM1LH, and got the no such partition error when I try to flash everything. I googled a lot and no miracle cames, so I just use the command that specified slot (which means I go over all the commands with specifying the slot a at first time and with slot b at second time) , it seems that all images can be flashed into slot a and b at this way except system image, but I re-flashed the system image to slot a and b successfully after flash all other images. And now I get my phone at DP 3, all functions work fine except the serial number is still a strange one. Hope this is useful to help you since I know it is really a bad feeling when the phone seems bricked. Also a hint is when you flash the image with specifying the slot, you may also get the error which says error remote flashing (maybe not accurate), I just re-ran the command and it works. Since English is not my native language, if any thing has grammar error please just ignore it.

MRR0GERS said:
I woke up to the OTA for the latest Android P update on my Essential phone this morning. Like a kid at Christmas, I couldn't wait. I started the OTA download and shortly after the download finished the install failed. So I tried it again thinking maybe there was a hiccup in the download, same result. Once I got home from work I figured I'd just download the fastboot image from the site and try that. Going through the steps as listed and all of a sudden random images would fail on flashing. All of the images flashed with the exception of boot, system and vendor.
What really has me worried is that the product name, bootloader version and serial number are all showing differently now afterwards.. which has me really worried that the phone is toast. I'm very careful with my devices; they aren't dropped and are always in a case with a screen protector. I'm not new to flashing roms or updates, I've been doing this for years and never had a problem.. and before someone asks, yes, flashing unlock and flashing unlock_critical was done before I started flashing the different partitions.
Click to expand...
Click to collapse
It seems I have the same problem. After flashing the latest Android P beta DP3 through fastboot, some images like system and vendor didn't flash on the first attempt for me. After multiple bootloader reboots I managed to flash everything one by one, but phone's serial number is completely messed up. At first I didn't notice this and continued to configure and use the phone for half a day since I'm on wifi, but then I realized the network is not working either. That is, it shows either no network or zero bars and I cannot place calls or use data. The situation with the network was the same when I flashed Oreo images. I checked my sim card works with another phone, and a sim card from my friend also didn't work with my phone. Could it be due to a weird serial number? If so, how do we revert it back?

What exactly is the error message when you flash those partitions? AFAIK those partitions are the big ones that give a warning about sparse header size which should just be ignored

craznazn said:
What exactly is the error message when you flash those partitions? AFAIK those partitions are the big ones that give a warning about sparse header size which should just be ignored
Click to expand...
Click to collapse
I honestly don't recall what the exact error was.. That being said, there was a new release of the platform tools after I had posted so I installed those, tried again and successfully restored the device to working order!

Which platform tools did you get? Mine are all dated 5/22/2018 after I updated... but for some reason I had to manually flash both sides... for some reason, I get an error trying to flash like this:
fastboot flash nvdef nvdef.img
The error looks like this:
Writing 'nvdef__a' FAILED (remote: No such partition.
But this works for me:
fastboot flash nvdef_a nvdef.img
fastboot flash nvdef_b nvdef.img
If a new/different set of platform tools fixes this, that'd be great.

Has anyone found a solution to this? Namely, did you manage to change back your serial number? I still have no network on my phone, I don't know if it's related.

[SOLVED] Cascading failures leading to bootloop and softbrick

Hello all. I am about done with this phone. Let me give you a quick timeline.
I had a bootloader error, so I flashed the NPN25.137-35 images to get it working
I used it for about 1 week, installing all of the OTA security updates
One morning, my phone had restarted (I know because "You must enter your pattern after a restart")
Over the course of this day, google apps starting force closing and opening some of them would soft reboot the phone.
The next day, random apps were doing it too
Finally, after one crash, the OS never came back up, it was bootlooping
Upon a hard restart, the phone only boots into bootloader.
This is where I am now. I have downloaded NPN...35-5, NPNS...93-10, and NPNS...92.14. Unfortunately, trying to flash any of these give me a "prevaildation failed security update downgrade" error on every partition I try to flash. The phone just bootloops when I try to restart it.
Things I have tried:
Using fastboot to manually install one of the 3 packages mentioned above.
Using a toolkit to automate the install of the 3 packages.
Using Motorola Device Manager (Never got it to launch)
Flashing the blankflash bin (No usable image file found)
Android OEM unlock setting was not set before this crash, so I cannot unlock the bootloader.
Praying to various deities.
Unzipping the packages, editing the *info.txt file into androidinfo.txt and rezipping to use as an update package (Invalid info.txt error)
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
=~=~=~=~= SOLUTION FOUND =~=~=~=~=
This may not be a good solution for anyone else that has this issue, but recently Oreo came out and the OTA update was captured. I was able to flash the new OTA because it had a higher security level and at least got the phone bootable.

Do you know what software channel you were on? E.g. retus, retla, etc? If your phone was completely up to date with the OTA, then you can't use a firmware version of less than 92-14 or 93-14. Whether or not you use 92 or 93 depends on the channel.
Locked bootloader limits other possibilities unfortunately.

Retus. I can't guarantee it, but that looks familiar to me, like I had seen it somewhere in the "about phone" section. Is there a released Stock image that has the current security patch? I can't find it on XDA and I'm not trusting androidfixfiles.info or a link in a youtube video.

93-14 hasn't been leaked yet. So you'll be stuck for now.

Kilo__ said:
I have no idea what to do next. I find it frustrating that Motorola doesn't differentiate between 32GB, 64GB, Amazon ads, no amazon ads, US, EU, or indian variant in it's model numbers! Everything is just "XT1687" and none of the update files are named with words, so knowing what the hell I'm flashing is impossible.
So, frustrations aside, does anyone have any suggestions as to how I can get this phone working again. On a side note, the only thing that I can think of that would cause such a cascading failure from Stock OS is RAM or Storage corruption / failing. Any thoughts on that as well?
Click to expand...
Click to collapse
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.

pastorbob62 said:
As a last resort you might try booting TWRP in fastboot mode, download and flash the TWRP flashable version of NPNS25.137-93-14. and see if that gets you back to a working phone. Just a suggestion. I don't know if it will boot when the bootloader is locked but it is worth a try.
Click to expand...
Click to collapse
The phone was completely stock. It has the stock recovery and bootloader.

Kilo__ said:
The phone was completely stock. It has the stock recovery and bootloader.
Click to expand...
Click to collapse
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?

pastorbob62 said:
I get that. What I am suggesting is not installing TWRP, but booting it from fastboot, if it is even possible. Given your results trying to flash a ROM I would say not. But what do you have to lose by trying?
Click to expand...
Click to collapse
I've tried that with a locked bootloader myself, it doesn't allow a non-signed image to boot. OP should give it a go as a 'hail Mary' attempt, but I wouldn't be holding my breath.

I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.

jhs39 said:
I've never heard of a phone that was fully stock with no mods or flashing ever done on it getting a bootloader error. The only bootloader error I am aware of is when the bootloader and ROM build are mismatched which doesn't happen unless the phone is being manually flashed. Was the phone on a custom ROM and you tried to return to full stock? Did you purchase the phone used?
If no to both exactly what did you see when you got the bootloader error? What was the message and what was the phone doing?
People who are on full stock with a locked bootloader don't usually flash system images so your story is a little hard for me to understand unless there is more to it. Normally a factory reset would be the logical solution when your phone is acting odd--flashing a system image seems pretty extreme and it sounds like flashing the wrong system image might be the cause of your current problems.
Click to expand...
Click to collapse
I agree. :good:

While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what

Kilo__ said:
While my phone was wholly stock, I am not new to phone rooting or custom ROMS. I bought the phone from someone who was trying to unlock it. They screwed something up and couldn't get the phone to boot. I bought it, flashed the NPN25.137-35 image after reading plenty of XDA posts about it. This one was the Retus / North America stock image. Flashed using the suggested guidelines that are along the lines of "fb_oem_mode ... flash oem oem.bin ... flash partition sparsechunk1.img" (Something like that). That got it running and once booted, it had many OTAs update in quick succession. After about a week the phone started having trouble. Google apps would crash frequently, then non-google apps started crashing and restarting my phone. After one said restart, the phone would only bootloop. I tried rebooting into recovery to do a factory reset and got the bootloader instead. I can go take a look at the bootloader and see if it says it's secure / oem or what
Click to expand...
Click to collapse
Try flashing just the stock recovery, as it sounds like that is corrupt. Ideally you'd want to get a recovery that was the same build as you were on after all the OTAs had installed. At least you'd hope that that would give you the factory reset option.
If that doesn't work, there's fastboot commands to erase user data, cache, which would be pretty much what a factory reset would do. Hope you had your data backed up.

Oreo OTA came out recently. Someone grabbed the update file and uploaded it. I was able to flash it and get the phone to boot. The verdict is still out on if it'll be stable.

After Pie: Bootloader unlocked & TWRP install didn't work

Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!

cyrrel said:
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637

Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks

cyrrel said:
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
Click to expand...
Click to collapse
can you explain us the procedures that you have followed to downgrade. It would be really helpful. i have tried this
method but it didn't work for me. i am facing IMEI 0/no signal issues using this method.
Thanks

well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember

cyrrel said:
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
Click to expand...
Click to collapse
Are your imei & mac same as original? won't the imei/mac get affected by restoring someone else efs?

I don't know about mac, but imei is ok