How to go back from 21build to 00 build !!!!! - Streak 5 Android Development

Hi
Here is the process. But, please, don’t ask me how to be root or how to use fastboot … reader other threads for that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is only to go back from 21 to 00 builds
Download the official update 4399 from HERE
Copy this update to the root of your sdcard and rename it update.pkg
Download this zip HERE
Unzip it on your desktop
Put your streak in fastboot mode
Go to the directory where are the files from recovery rar and execute the right cmd for your situation :
fastboot-yourOS -i 0x413c flash recovery recovery.stock.new.img
push the the 2 volume buttons and at the same time execute the right cmd for your situtation :
fastboot-yourOS -i 0x413c reboot
Choose update from sd card …. And after the process you have now a 4399 21 build
Root your streak and install a browser like root explorer and a terminal from de market
Download the official 6267 build HERE
and copy it to the root of your sdcard
Rename the file as update.pkg
Download this file at the root of your sd card HERE
Download this zip and unzip it where your want on your sdcard HERE
then mount your / as rw and copy all the files unziped at the same place on the streak (etc to /etc, system to /system ...)
Form a terminal on your streak with su rights execute this
flash_image boot /sdcard/boot.img
Reboot your streak in normal mode
Reboot your streak in recovery mode and apply the update from sdcard
Would just like to say i have had no hand in this
It was all done by our good Friend GEEK78
And what a great job he has done thanks Mate

Is this only for Euro unlocked version or will this also work for AT&T Beta streaks from o2 leaked Rom to 1.6

cue_32 said:
Is this only for Euro unlocked version or will this also work for AT&T Beta streaks from o2 leaked Rom to 1.6
Click to expand...
Click to collapse
For 00 only but you have a similar thread for att devices

Can somebody help me? I always get to this poing:
Form a terminal on your streak with su rights execute this
flash_image boot /sdcard/boot.img
and than i am stuck i downloaded android terminal pro. wrote exactly command how it is here but i am getting erroroutput[usage: flash_image partition file.img
i am not a linux user and android is first linux i am trying
pls help

Maradar said:
Can somebody help me? I always get to this poing:
Form a terminal on your streak with su rights execute this
flash_image boot /sdcard/boot.img
and than i am stuck i downloaded android terminal pro. wrote exactly command how it is here but i am getting erroroutput[usage: flash_image partition file.img
i am not a linux user and android is first linux i am trying
pls help
Click to expand...
Click to collapse
Have you rooted the phone if so did you put SU in the terminal app and did it come up saying it has rooting permissions then a # comes up if so then thats when you put in the command and have you copied all the things into the right places as it says

404 error
Looks like Dell removed the link to 626700 http://mobileupdate.dell.com/LatestBuild/Streak_111_6267_00.pkg ; anyone happens to have the file saved and could kindly reupload it somewhere? just want to make sure to have everything ready in case something goes bad in the future... thanks

All files re-uploaded
http://hotfile.com/dl/70343149/ca9cfd6/recovery6267.img.html
http://hotfile.com/dl/70346274/b9b68f4/Streak_111_6267_00.pkg.html
http://hotfile.com/dl/70346615/2e02948/boot.img.html
http://hotfile.com/dl/70346681/ee5ded5/recovery6767_00.zip.html
http://hotfile.com/dl/70350376/62d95ea/Streak_104_4399_21.pkg.html

Thank you very much!!!

cant execute boot.img from su terminal always gets error my device is rooted plz plz plz plz help

yes,yes thanks
my divace 00

lufc said:
Hi
.....
Download the official 6267 build http://www.megaupload.com/?d=IU4OYAYQ and copy it to the root of your sdcard
Rename the file as update.pkg
Download this file at the root of your sd card http://www.megaupload.com/?d=8F8JBU1Y
Download this zip and unzip it where your want on your sdcard http://www.megaupload.com/?d=GPU0UPRB, then mount your / as rw and copy all the files unziped at the same place on the streak (etc to /etc, system to /system ...)
Form a terminal on your streak with su rights execute this
flash_image boot /sdcard/boot.img
Reboot your streak in normal mode
Reboot your streak in recovery mode and apply the update from sdcard
Would just like to say i have had no hand in this
It was all done by our good Friend GEEK78
And what a great job he has done thanks Mate
Click to expand...
Click to collapse
I did all this but when I restart in recovery and select option 2, the screen goes blank and nothing happens!
HELP!

geek78 said:
For 00 only but you have a similar thread for att devices
Click to expand...
Click to collapse
I can't seem to find the thread. Would you post the link? Thank you

OrionBG said:
I did all this but when I restart in recovery and select option 2, the screen goes blank and nothing happens!
HELP!
Click to expand...
Click to collapse
I have a similar issue now. I was successful at downgrading to 1.6 4399, but then made some errors and got flashing lights and FOTA model mismatch error. So I tried to start over with 4399 and now when I try to update the pkg in recovery I just get a blank screen and nothing happens. I hope someone will be able to help us out here. These blinking lights are driving me crazy.

Yes, you have this error because you should to follow the end of this tuto :
hxxp://android.modaco.com/content/dell-streak-streak-modaco-com/317549/how-to-go-back-from-21-to-00-builds/
=> replace hxxp by http
I have follow it and I am now with 6267 with 00-EU baseband.
But nothing happens (no notification and uptodate page from the manual update) for the official 2.2 update with this ROM...

mirrdhyn said:
Yes, you have this error because you should to follow the end of this tuto :
hxxp://android.modaco.com/content/dell-streak-streak-modaco-com/317549/how-to-go-back-from-21-to-00-builds/
=> replace hxxp by http
I have follow it and I am now with 6267 with 00-EU baseband.
But nothing happens (no notification and uptodate page from the manual update) for the official 2.2 update with this ROM...
Click to expand...
Click to collapse
Thank you, mirrdhyn!
So do I need to go back to Step 1 to re-install 4399 and then try to go to 6267? I ask because I know I made some mistakes and messed up the files in the system so I think I need to start over fresh to do it again. Correct? Please let me know how you got through your process when you can. Thank you in advance, good man!

I just tried reinstalling the 4399 to I can start fresh but after it completes recovery and reboots, when I try to update in recovery mode - the screen stays blank. Is it doing that because my build is already 4399 even though I messed some system files from earlier or am I doing something wrong again? I don't think I can get to the second part of the process (changing back to 00 baseband with flashing 6267 image) until I get my 4399 all fixed. Is this logical or am I missing something? If I can at least get to a normally working 4399 without flashing lights - I will be happy. I am just desperate to fix the errors I created when I tried to go into the second part of the tutorial (going to stock 6267). Please advise.

Hello,
I am not on my desk to type a lot of text to explain how to get the correct baseband with the version 6267.
But tomorrow morning I will do that for you.
Sorry for the delay.

mirrdhyn,
You wouldn't believe this. I did it!!! I got it to 6267 just like I had it when I first got it. I am so excited and relieved. I am going to try to post my steps which ended up being a combination of the steps in this thread, the German guys steps and from another thread on this forum that explained the steps of going to the US version.
In any case, thank you so much for replying back so quick, my friend. I can sleep now

streak4m3 said:
mirrdhyn,
You wouldn't believe this. I did it!!! I got it to 6267 just like I had it when I first got it. I am so excited and relieved. I am going to try to post my steps which ended up being a combination of the steps in this thread, the German guys steps and from another thread on this forum that explained the steps of going to the US version.
In any case, thank you so much for replying back so quick, my friend. I can sleep now
Click to expand...
Click to collapse
What is your OEM Version displayed in the "About device" screen?
I'm trying to forcefully get the update from Dell by imitating the device but I can not find a OEM version that isn't invalid or up to date.
I even tried brute forcing between GAUSB1A111000 and GAUSB1A111999.
Has anyone actually got the official update yet?????

Good job !
So, finally, it's not difficult to go back in 6267-00
@garrows :
I think that you spend your time.
I follow a lot of web sites and twitter and I can say that the official update is not here... I don't know why Dell has sent a lot of informations about this update if they don't release it...
Another possibilty, the official update arrives in two weeks for all and now for the UK beta testers. But, the UK beta testers have a NDA or put the streak in the bin

Related

X10 Custom ROM AOSP 2.2.1 : How to for dummies

SINCE FREE X10 IS NOW BETA, THIS HOW TO IS NO LONGER VALID
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
** No responsability for anything, you are all responsible of what you're doing !! **
** Please follow ALL these steps. Don't try to be Indiana Jones by flashing your device without all the tools needed !!! **
INSTALL
(for 1st install)
Before attempting anything, make sure you have AT LEAST 50% of battery charge. Don't try anything with low battery, you can abort the flashing and brick your device !!!
Please make sure you're also running a 2.1 rom (Generic, nordic, official, custom...)​
- Download FreeX10 v0.0.1 file (NOT 002 yet !!!)
- Download Android SDK
You don't need to save the entire archive (but you can), you just need the Tools folder (because it contains ADB, the Android Debug Bridge we need to install files).
- On x10 :
Download and install Busybox (from Market), make sure it says "Done!".
Connect your x10 in USB, mount SD card, and copy files FreeX10.zip and install on the root of your SD Card.
Enable USB debugging (Parameters > Applications > Development).
- On your computer, go in the Tools folder, open a DOS prompt (for Windows 7 : hold CAPS + right click, you'll see Open a DOS prompt) and
type :
Code:
adb shell
(this will run ADB shell... You will get a "$")
- Type :
Code:
su
(this will make you super-user, you will get a "#")
- Type :
Code:
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
(It will display "11", "1+1", or "inflating:..." ...)
- Wait, have a beer, pray for your sins for your phone not to turn into a $600 brick
- One minute after, when it shows
Code:
All done, please reboot!
, reboot ! (But you can gently quit ADB by typing
Code:
exit
twice
)
Note : regarding me, I typed "exit" to quit ADB, I turned off ADB on phone and disconnected USB. You can do, it's even safer
- Wait up to 5 minutes for the phone to boot, it is NORMAL !!!! It looks stuck on Sony Ericsson logo and/or on Free X10 logo, it's NOT stuck !!! You MUST wait !!!!
- It will finally run normal, your phone is alive and 2.2-hearted !!
You are now eligible to install v0.0.2 (as it comes as an update).
Dual Boot usage
This rom comes with a great Dual Boot, which means the 2.2.1 is installed safely apart from your original 2.1 rom. This means you can switch back anytime to stock rom. To say it simply :
- Your Android 2.1 is here, and no changes are made to it (apps, version, etc etc). It is stored as it has to be, in the internal 1Gb phone memory storage (called the "NAND").
- FreeX10 (2.2.1) is running from image files (like .ISO files) stored in your SD Card. This means the two Android are living together peacefully, without affecting (theorically) each other.
FreeX10 mainly creates a bootloader, for you to choose whether to test 2.2.1, or go back to 2.1 for your daily use.
- To run 2.2.1 : do nothing (default boot)
- To run 2.1 : press any key at boot, when it shows "Sony Ericsson".
Notes when upgrading to v0.0.2 :
- As Android is stored into image files (.IMG), upgrading will wipe out all your content (it does a fresh "install"), make backup of what you need !
- to avoid future bugs, altough you're not forced to do, do the routines to make sure Wifi, root, packages install, ... work. This is because USB debug can break, so you won't be able to use ADB to fix these bugs
- Root is strongly recommended to work, because it's cool and because the CPU performance is set to highest : stuck at 998MHz all the time, it will drain your battery like hell ! You can switch it back to original power saving plan (ondemand plan) by using (ie) SetCPU. Root required !
If your Android goes instable, does not work anymore, or you want a fresh install after lots of tests, simply drag and drop the original v0.0.2 .img files on your SD card. This will make you boot into a fully fresh install.
For all bugs, commands, etc.. Please go first to this excellent (and very easy) thread !!
Nice..
How about one on AOSP 2.1
Perceval from Hyrule said:
Hello world !
I noticed there was nothing to explain simply how to install the increible X10 Free Rom in dual-boot with your regular 2.1 rom of Zdzihu.
Click to expand...
Click to collapse
nice dummies HOW TO
and ohhh my god there is dummies
all comands needed
INSTALLATION
1. Download the rom package (FreeX10_alpha-release_0.0.1.tar.bz2)
2. Unpack it to the root (main folder) of your SD Card
3. Connect your phone in USB Debugging mode
4. Open ADB shell, switch to root user (SU)
5. Issue the command
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && ./data/install
6. Reboot when installation is finished
7. Enjoy
---------------------------------------------------------------------------------------------
CHANGE BOOT PRIORITY
Copy chargemon.txt file to
/system/bin
folder ON YOUR ORIGINAL 2.1 ROM, NOT FROYO!!!
---------------------------------------------------------------------------------------------
UPGRADE TO 0.0.2 VERSION
Boot into 2.1, unpack the content of FreeX10_alpha-release_0.0.2-UPDATE.tar.bz2 into
/sdcard/FreeX10
folder and reboot into updated 2.2!
NOTES:
1. SMS vibrate is disabled by default; open Messaging, press MENU button -> settings -> vibrate -> always
2. If you don't have radio (network) after 1st boot, please open ADB shell and issue this command:
killall servicemanager
3. If you don't have root access, please open ADB shell and issue this command:
chmod 4755 /system/bin/su
---------------------------------------------------------------------------------------------
hope it helps too
UPDATE TO v.0.0.2
Note : you can only update from 0.0.1 to 0.0.2. I mean you can't do a fresh install of 0.0.2, you MUST have 0.0.1 installed !
- Download v0.0.2 from main thread.
- Run your device on your regular 2.1 rom (while off, power on, and press any button when it displays Sony Ericsson logo)
- Mount the SD Card, then copy data.img and system.img from the archive into the folder /FreeX10. Replace the two .img files.
- Reboot into 2.2, have fun ^^
OmegaRED^ said:
Nice..
How about one on AOSP 2.1
Click to expand...
Click to collapse
I'll try to do one if I get time, but I need a fully working ROM as my phone is useful for my life (still waiting for 2.1 stable )
Thanks for your posts all, it will help everybody who want to try the 2.2
(as it is safe and running from SD card, very very very cool idea !)
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
root privileges do you have it?
unmount sdcard
OmegaRED^ said:
I found drawing a pentagram in human blood and chanting a few words can do wonders too.
Click to expand...
Click to collapse
sarcasm...love it
rendeiro2005 said:
root privileges do you have it?
unmount sdcard
Click to expand...
Click to collapse
yes mate i do have root access titanium etc works fine just cant get adb shell to run
When i installed 2.2, it rebooted and when to the sony ericsson logo for almost an hour, does this mean i have to reinstall 2.1, and if so, i would i accomplish this
fastphil said:
yes mate i do have root access titanium etc works fine just cant get adb shell to run
Click to expand...
Click to collapse
and what about sdcard?
uncheck nount/unmount
rendeiro2005 said:
and what about sdcard?
uncheck nount/unmount
Click to expand...
Click to collapse
done that too
fastphil said:
done that too
Click to expand...
Click to collapse
can you post a screenshot of cmd?
ok will do
I am still having problems also...
after I type the cmd...
dd if=/sdcard/install of=/data/install && chmod 777 /data/install && /data/install
it just says:
1+1 records in
1+1 records out
520 bytes transferred in 0.003 secs...
#
so, where am I going wrong?
fyi, I am trying to install v001, not the update, and the phone is rooted, busybox is installed. Sorry, but I have tried for a while now and I finally have to just ask for help. Thanks guys.
here pic off cmd
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fastphil said:
Help followed your guide get adb shell not a internal command what am i doing wrong been trying this for hours now
Click to expand...
Click to collapse
Does it work when your run "adb" command only ?
It looks to me your error is because you're not in the folder where adb.exe is
It is in folder tools, if you try to run it from root directory (where is the android app with nice icon) it won't work for sure
Edit: didn't see your screenshot >> you are NOT in the correct folder !! (so Windows is searching for a registered command which does not exist, I think there's a thread somewhere on how to add it as a registered (I mean global) command)
You must download Android SDK (22mb... Lmao regarding 4gb for iOS ), extract the archive and go in the tools folder. Here is adb.exe.
when i try & run adb exe it does not open it just closes right away

[Q] Wifi not working on NegaLite?

Hi all. I bought my Evo 3D phone from someone and the wifi is not working. Trying to turn it on just results in "Error". Apparently this is rooted and/or has custom firmware. The software is NegaLite BluROM with android 4.0.3. I was wondering if anyone could help a root/cfw newbie with step by step instructions on how to get wifi working again. My google research showed something about a Mobster ROM being the best firmware, but have no idea about anything.
i like negalite the best, but what release is it?
i also liked mobster lite and unsenseable.
negalite blurom cdma vm r115
try the official thread here:
http://forum.xda-developers.com/showthread.php?t=1745093
i use jcfunk's fork, its more recent and you might even get something hot off the press if you check out his svn.
midnight rom deserves a mention:
http://forum.xda-developers.com/showthread.php?t=2141207
i'm not sure where mobster went, i'll hunt a link down later if you need. same with unsenseable.
jawbonegroove said:
try the official thread here:
http://forum.xda-developers.com/showthread.php?t=1745093
i use jcfunk's fork, its more recent and you might even get something hot off the press if you check out his svn.
midnight rom deserves a mention:
http://forum.xda-developers.com/showthread.php?t=2141207
i'm not sure where mobster went, i'll hunt a link down later if you need. same with unsenseable.
Click to expand...
Click to collapse
I yes, latest is on svn, but latest zip negalite-funk_mod_v3.zip
hey jcfunk i replied to the official thread. i tried the update but wifi still won't work
Are you s-off or just unlocked?
jcfunk said:
Are you s-off or just unlocked?
Click to expand...
Click to collapse
i never knew what s-off was. i rebooted into recovery and it turns out i have s-on. then i googled and found Unrevoked, but the download doesn't work.
Here I can quick fix your phone, download recovery on computer.
ReBoot phone into bootloader.
From computer,
fastboot boot recovery.img
This will upload recovery.img to phone, and boot recovery with write access to boot partition. Which HTC has locked, this is first method found to by pass. Other would be dumb-lock. But that's your wifi issue, because your still using stock kernel, but wifi drivers are built for my kernel
jcfunk said:
Here I can quick fix your phone, download recovery on computer.
it just says Bootloader, Reboot, Reboot Bootloader. those are my options i'm not sure what to do
Click to expand...
Click to collapse
Also, can use Flashify to install a boot.img but won't work with installer zip for my kernel, because boot.img is made during install.
May look like this, fastboot shows when usb is plugged in.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yeah the screens look like that but i tried all the options. i don't know how to install your image
InvisiSource said:
Home of the ORIGINAL hboot 1.50 'how to flash'
less than 48 hours after HTC released their web based unlocker, i walked a user thru the process below in public chat (the public Synergy Chat room) - two hours later some one posted it on XDA and claimed creait for it, even copied/pasted my spelling errors. when called out with screen shots of the chat with timestamps, they still claimed credit. - this is the ORIGINAL.
This is a cleaned up and detailed version of the chat, I included it as 2nd post to my roms and always posted it when someone needed help. so a few weeks later, i finally decided to make a post here.
---
so, you unlocked using HTC's unlocker located at HTCDEV.com
some background on this unlock method:
-when you unlock using HTC's unlock method, the boot partition is still read only, and you cant flash to it. (kernels and ramdisks go here - so no 2.3.3 rom will boot, and most 2.3.4 roms will not work correctly)
when you unlocked your bootloader using HTC's method, you should have downloaded a file that contained some program files, mainly fastboot.exe and adb.exe, as well as the device drivers you would have to install to unlock
- you will need these
to get around this problem HTC has created, we will be using the fastboot.exe program to force the ramdisk/kernel onto the phone. anytime you use fastboot to flash a partition, you risk bricking your phone, so please do this at your own risk.
I have walked several people thru this, and no one had any problems, but if something dont go right, or the connection between the pc and the phone gets interrupted, your phone may become bricked.
I am going to assume you know the basics of flashing a rom, and that you have either teamwin or clockwork's recover tool installed on your phone (and you know how to use them). if not please see series #3 below.
SERIES 1 - INSTALL A ROM AND RAMDISK/KERNEL
Step 1 - backup everything on your phone, nandroid backup
step 2 - if you want to flash the ext4 optimizer for /data, read the info and directions here -> http://forum.xda-developers.com/show...postcount=6329
------>everything should be backed up now
Step 3 - flash Virus's superwipe tool.
Step 4 - flash the /data optimizer tool - the download can be found in the post linked in step 2
Step 5 - open the rom you downloaded using winrar, or 7zip, and copy the boot.img file somewhere (the same folder that contains the tools you used to unlock your phone would be a perfect place)
Step 6 - open a command prompt (or terminal window), and goto the window that contains the tools you used to unlock your boot loader
Step 7 - reboot your phone into fastboot (adb reboot bootloader)
Step 8 - from the command prompt enter the following command:
fastboot flash boot boot.img
then press [enter]
Step 9 - once complete, exit fastboot, and boot back into recovery
Step 10 - flash the rom's zip file using recovery
Step 11 - enjoy
SERIES 2 - INSTALL A RAMDISK/KERNEL (ROM ALREADY FLASHED)
*signs of a failed ramdisk flash include broken wifi, 4g, poor performance and just weirdness in general. the updater scripts used to install a rom will not flash ramdisk with S-ON.
Step 1 - open the rom you downloaded using winrar, or 7zip, and copy the boot.img file somewhere (the same folder that contains the tools you used to unlock your phone would be a perfect place)
Step 2 - open a command prompt (or terminal window), and goto the window that contains the tools you used to unlock your boot loader
Step 3 - reboot your phone into fastboot (abd reboot bootloader)
Step 4 - from the command prompt enter the following command:
fastboot flash boot boot.img
then press [enter]
Step 5 - reboot your phone and enjoy (fastboot reboot)
SERIES 3 - INSTALL A RECOVERY TOOL
*you may need to do this before each flash, some phones somehow break recovery after a rom is flashed, and recovery will not launch until re-flashed for some reason (Kathy.. )
Step 1 - download TeamWin's recovery here (IMG format) -> http://dl.dropbox.com/u/24995663/recovery.img
Step 2 - copy this file to the same directory as your fastboot and adb files HTC had you download to unlock your phone.
Step 3 - goto your dos prompt (or terminal if on linux)
Step 4 - change directories to the folder your files are in (recovery.img and fastboot)
Step 5 - flash your recovery using the following command
fastboot flash recovery recovery.img
Step 6 - reboot your phone (fastboot reboot)
*disclaimer - you do this at your own risk. as of yet, the processes listed above work 100% and not 1 failure has been reported. make sure your usb cable is good, and your pc has good power during any fastboot process. most of this comes from a chat i had in the synergy public/general chat room 2 hours prior to it being posted on XDA by others claiming credit. kangers goto hell.
fastboot for mac and linux attached below:
ADB and FASTBOOT for windows:
View attachment 330
Click to expand...
Click to collapse
Here is a quote from other site
I assume Series 3 is the part I need to follow? Do I do this during recovery mode or normal phone mode? Because I don't know the file directory of my phone
kracovwolf said:
I assume Series 3 is the part I need to follow? Do I do this during recovery mode or normal phone mode? Because I don't know the file directory of my phone
Click to expand...
Click to collapse
Yes, but post was very old, use recovery I posted. Also if you use command
Code:
fastboot boot recovery.img
instead of
Code:
fastboot flash recovery recovery.img
It will load/run recovery from computer, then install kernel from recovery.
Who took the credit for your guide?, just wondering
PiggyFlooper said:
Who took the credit for your guide?, just wondering
Click to expand...
Click to collapse
What do you mean? The quote I posted?

Root the ZTE Nubia Z9 Classic

Hello,
Custom Recovery + Root​
Wolfpapa said:
this is new: Nubia z9 全球首发中文TWRP recovery 以及root工具 时
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://bbs.nubia.cn/thread-501293-1-1.html
Download: http://pan.baidu.com/s/1ntoX6AX
Click to expand...
Click to collapse
Google Play​
Wolfpapa said:
Works! Thanks!
BASIS: http://bbs.nubia.cn/thread-487610-1-1.html
1: ROOT :
http://bbs.nubia.cn/forum.php?mod=viewthread&tid=480787&extra=page=1&filter=typeid&typeid=379
2: Step by step BASIS
3: manually installed pack of gapps called : system\priv-app folder with rwxr-xr-x permissions.
4: Reboot
5: run Play Store (After it sets long to start: new reboot)
6: enjoy! ALL WORKS! (also contacts)
Click to expand...
Click to collapse
Custom ROM from Cuoco92​
Cuoco92 said:
Here the 1.38
https://mega.nz/#!O4pHVZgB!Q4bqcygWox9GAZWfhiWviUX34OGnwXPfK7fXq5-RLd4
I've posted it on my Facebook site
https://m.facebook.com/cuoco92
Inviato dal mio NX505J utilizzando Tapatalk
Click to expand...
Click to collapse
Let me know what works for you. Just got mine today and have tried root genius and kingroot..no luck
Akuji52 said:
Hello,
i want to root the ZTE Nubia Z9 but nothing works. I tried Rootgenius, Kingoroot ...
Can someone help ?
Thank you
Click to expand...
Click to collapse
it worked today!
http://bbs.nubia.cn/thread-481008-1-1.html
Download:
http://pan.baidu.com/s/1c0k3O9E Password: mk24
Google apps:
http://www.coolapk.com/apk/org.coolapk.gmsinstaller?from=rss&version=1.0.0-beta4
UPDATE!
http://forum.xda-developers.com/showpost.php?p=61779046&postcount=86
Hi Wolfpapa,
thank you for your info.
I downloaded the files you write.
But now i can not read the chines letters. How did you make it, with the .exe file.
Can you please write it in english or german.
Thank you!
Grisu122122 said:
Hi Wolfpapa,
thank you for your info.
I downloaded the files you write.
But now i can not read the chines letters. How did you make it, with the .exe file.
Can you please write it in english or german.
Click to expand...
Click to collapse
the same as in (can it also work ...) :
http://forum.xda-developers.com/and...-nubia-z9-mini-one-click-root-custom-t3130631
Original " Z9和Z9MAX 是一个ROOT工具 " version:
It may be the exception to the non-English speaking TWRP VERSION...
Here is the solution to English translation:
http://forum.xda-developers.com/showthread.php?t=2373952
Unfortunately, I can test the next week. The phone will be next week delivery
please write about your experiences phone! Google apps ?
Thanks!
New FOTA UPDATE About SD!
Back up your data before moving to a new rom !
http://www.nubia.cn/service.php?sid=5
Download: Password : tira
http://pan.baidu.com/share/link?shareid=3545574096&uk=2436317143 (Jdownloader )
Update PDF manual:
http://pan.baidu.com/s/1c0wGeMc
first Steps!!!: UNROOT !!!
step Two: reading PDF :laugh:
i killed my stock recovery so i cant go to the recovery to update. It shows only a black screen.
Is there a way to flash the stock recovery or a custom recovery ?
I have root.
Thanks
Akuji52 said:
i killed my stock recovery so i cant go to the recovery to update. It shows only a black screen.
Is there a way to flash the stock recovery or a custom recovery ?
I have root.
Thanks
Click to expand...
Click to collapse
post #6 !!! - or.. :
1; download rom post #6
2; Unpacking with WinRAR or 7zip the stock recovery.img
3; fastboot mode ( enable USB Debugging mode )
4; Flashing recovery.img via adb
ok thanks, i will try it , when i am back from holiday
Wolfpapa said:
post #6 !!! - or.. :
1; download rom post #6
2; Unpacking with WinRAR or 7zip the stock recovery.img
3; fastboot mode ( enable USB Debugging mode )
4; Flashing recovery.img via adb
Click to expand...
Click to collapse
don't try this!!!!
i have flash the recovery.img file and now the phone doesn't start!!
i cant only start on boot to choise recovery or normal boot but don't work in all two options!!!
HELP ME!
NMarco said:
don't try this!!!!
i have flash the recovery.img file and now the phone doesn't start!!
i cant only start on boot to choise recovery or normal boot but don't work in all two options!!!
HELP ME!
Click to expand...
Click to collapse
How this happened?It describes the process?
why, how? etc.
I have used recovery.img into the upgrade file.
Flashed via adb and now the phone is hold on boot logo screen.
If I power on pressing vol - button I see screen to choose to boot in recovery or reboot system or power off.
All options doesn't work!
Do you have any ideas?
wow!!! Solved!
- I waited until the battery of my nubia z9 was completely to 0% .
- pressed vol down and connected to usb cable + charger (not pc!)
- wait 10 minutes for charge a little battery
- connect phone to pc and extracted recovery.img of the file zip upgrade
- via adb I have run this command: fastboot -i 0x19d2 flash recovery recovery.img
- selected reboot to recovery
- ALL OK! fortunately!!!
NMarco said:
wow!!! Solved!
- I waited until the battery of my nubia z9 was completely to 0% .
- pressed vol down and connected to usb cable + charger (not pc!)
- wait 10 minutes for charge a little battery
- connect phone to pc and extracted recovery.img of the file zip upgrade
- via adb I have run this command: fastboot -i 0x19d2 flash recovery recovery.img
- selected reboot to recovery
- ALL OK! fortunately!!!
Click to expand...
Click to collapse
cleverly solved! :good::good::good:
any ideas to install gapps without custom recovery?
ok! in this post I reply to me!!
I have manually installed pack of gapps called: gapps-lp-20141109-signed on system\priv-app folder with rwxr-xr-x permissions.
That's all!
All works but actually only contacts aren't not sync and I dont's see in sync page of my account.
How did you actually do it?? It's not clear to me, are you rooted? Otherwise how could you access "system\priv-app" folder?
Thanks...
Yes, device is rooted!
NMarco said:
Yes, device is rooted!
Click to expand...
Click to collapse
And can I ask the exact steps you took?
Thanks again...
---------- Post added at 09:45 PM ---------- Previous post was at 09:28 PM ----------
giacomofisico said:
And can I ask the exact steps you took?
Thanks again...
Click to expand...
Click to collapse
Getting specific, is it the boot.img that you find in the big .zip file that you have to boot up?
Something like:
adb reboot bootloader
fastboot -i 0x19d2 boot boot.img
...and then flash superSU (and possibly gapps)?
Hi All.
Got my device from Hong kong today, Live in Denmark so think i am the first user in Denmark of this device.
Man the screen are great
We are missing an forum for this device here on XDA, hope they create one for us soon, so we can setup guides on how to do this and that.
Ok could we create an process guide in this thread with links for updating, rooting and so on.
I really miss Google stuff on my device, Google Play, sync from google contacts, photos, calender and so on.
First i think i need to Root right?
When its done i need to install Google framework right?
Could soneone that has allready provide us with links, guides or mayby Youtube video on how to do it correct, i would kill myself if i Break the device on the first day.
Thanks peeps

[RECOVERY] TWRP 3.0.0.0 for D605

Team Win Recovery Project v3.0.0.0 for D605
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HOW TO INSTALL:
Flash from old recovery:
Reboot to your current recovery.
And flash the archive.
Flash recovery.img without custom recovery:
Extract contents on your PC
Copy loki_flash and recovery.img to you phone's SD card via MTP connection
Download and start Android Terminal Emulator from Play Store
From terminal emulator type: $ su
Then type (assuming files from zip were copied to external SD card root) :
# cp /storage/external_SD/loki_flash /storage/external_SD/recovery.img /data/local/tmp
# cd /data/local/tmp
# chmod 777 loki_flash
# ./loki_flash recovery recovery.img
# reboot recovery
DOWNLOAD:
Link to flash from recovery:
https://mega.nz/#!fo8DCDbb!wvN9GTN7xzuTGnNMBfu4UwmAo7culclt88qb-qJoZLI
Link to flash without recovery:
https://mega.nz/#!y1dk0KwS!HAwU-Pi6jgfQPe3c1yID9WmX76X_afdNpTpToPbfqSA
STATUS:
Stable (but I have not tested)
Nice work, thx (will you end cm12?)
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Downgrade to jb
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Ag0n1a said:
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Click to expand...
Click to collapse
I have win 10. And i bricked (Hard) LG l9 II
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Ag0n1a said:
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Click to expand...
Click to collapse
I don't know where you guys get your information from but stop saying phones are not possible to hard brick and spread this word around. It is very easy to hardbrick any phone with root.
I will go just in a little bit of detail to show you.
How does your computer boot?
The hardware you have (CPU, GPU, Memory etc) are searched for (physical addresses) by the motherboard by the BIOS. Delete or erase the BIOS and I bet you any sum that your computer will stop doing anything (starts and sits idle just fans spinning).
With this analogy the BIOS of any mobile device is the bootloader. In the bootloader, that is located on the eMMC (embedded Multi Media Controller; like an SSD but with the controller of memory in the silicon die). eMMC is partitioned like a hard disk.
Your phone has an integrated Primary Loader in the CPU (this is what Qcom 9008 is). By shorting pins you change the boot order. If you short correct pins you can send data into memory (RAM) from the CPU and then write it on the eMMC (if you have the correct communication). This is where the HEX programmer comes in. This is how Qualcomm tools know how to communicate with the SOC.
The 2nd loader is on the eMMC. By default all CPU's boot from eMMC. SBL1->aboot and so on is the bootchain. Where hardware is initialized and recognized. Destroy and of those partitions and you will have a hardbrick (either fallback to 9008 automatically because eMMC is empty or not recognized at all).
Well I ended up giving you kind of a full information. Just stop trowing around this thing "phones can't be hardbricked". Hardbrick describes the state where a phone can't enter the last emergency mode provided by the manufacture (Emergency in this case). And generally buttons don't work, screen isn't either and so on.
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Ag0n1a said:
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Click to expand...
Click to collapse
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
A
neutrondev said:
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
Click to expand...
Click to collapse
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Ag0n1a said:
A
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Click to expand...
Click to collapse
Yeah you are right. That is just a message it will not flash it for you. But if you see that message and try to flash a lower aboot without flashing full KDZ you are in big trouble.
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
AWESOME1092387456 said:
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
Click to expand...
Click to collapse
For me the installation works but don't install it... i've installed cm12 and it sayed secure booting failed
and backup/restore doesn't work, it corrupted /data partition but i resolved it.
Kaszke said:
Downgrade to jb
Click to expand...
Click to collapse
How? I couldn't find a working link for a stock jb.
Cristi73 said:
How? I couldn't find a working link for a stock jb.
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=37
Find the kdz that coresponds to your region/carrier.
goooooooooD!!!! amazing job ))))
JackPOtaTo said:
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Click to expand...
Click to collapse
hey here is the solution body
II Flash
GOTO D605 RECOVRY (folder) hold shift and right click on the mouse then open window command here
then copy the commands on the cmd
you need to have adb driver installed and here the download link http://www.mediafire.com/download/u6pdpy77sonjyqh/D605+RECOVRY.rar
1 adb push aboot.img /data/local/tmp
2 adb shell
3 su
4 dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4 exit
5 exit
6 adb push loki_flash /data/local/tmp
7 adb push recovery.img /data/local/tmp
8 adb shell
9 su
10 cd /data/local/tmp
11 chmod 777 loki_flash
12 ./loki_flash recovery recovery.img
13 reboot recovery
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
sedi21 said:
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
Click to expand...
Click to collapse
but how did you unlock it? because i don't know how to unlock mine and i don't think its possible

[GUIDE] How to dump boot image and root Nokia 3.2 / 4.2

If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
So after you unlock the bootloader successfully, you definitely want to install custom ROM, or at least root the phone, right?
Here's the guide about rooting Nokia 3.2 / 4.2.
This guide could probably work on Nokia 6.2 / 7.2 in the future.
Step 1: Unlock the bootloader
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
For Nokia 3.2, you'll need to read this as well: https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841
Step 2: Acknowledge current slot
You have two methods.
Method 1: After USB debugging enabled, execute this command:
Code:
adb shell getprop ro.boot.slot_suffix
Method 2: Under fastboot mode, execute this command:
Code:
fastboot getvar current-slot
We assume the current slot is b.
Step 3: Trigger the phone to EDL mode again
There's a hidden command in aboot known as "fastboot reboot-emergency".
However, normal fastboot binary doesn't have that command at all, so we need to compile a binary or hack the binary.
For Windows users, I've provided the fastboot binary that can use this command, and I renamed it to edl-fastboot.exe. You can download it on the attachment below.
For macOS/Linux distro users, I'm afraid you have to fork the source code, edit related content and compile yourself.
So with this special version of fastboot binary, we can boot the phone to EDL mode directly:
Code:
edl-fastboot.exe reboot-emergency
But wait, why didn't you mention this command when you released bootloader unlock guide?
That's because, if you attempt to use this command under locked bootloader, bootloader will response "Permission denied, auth needed. " and refuse to proceed the command.
I don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
Click to expand...
Click to collapse
Step 4: Use partition manager to dump the partition
If you've came so far when unlocking the bootloader, you have already know the great partition manager.
Still, we assume the COM port number is 8 (COM8).
When the partition list appears, find "boot_b" (or boot_a if the current slot is a), right click on it, choose "Manage Partition Data" and click "Read Data". Then fh_loader binary will dump the boot image to your PC.
For Windows users, it's located at
Code:
%AppData%\Qualcomm\QFIL\COMPORT_8
Where %AppData% is actually C:\Users\your_user_name\AppData\Roaming .
The filename looks like this: ReadData_emmc_Lun0_0x3a000_Len65536_DT_07_09_2019_13_55_54.bin
Now close the partition manager, your phone will exit EDL mode and boot normally.
If you're interested in dumping full eMMC storage, you may want to read this: https://forum.xda-developers.com/android/general/guide-how-to-dump-write-storage-t3949588
Step 5: Install Magisk Manager and patch the boot image you dumped
I think everyone who reading this guide knows where to download Magisk Manager.
Copy the boot image you dumped with QFIL to Download directory in your phone's internal storage, and rename it to boot.img for your convenience.
In case you don't know how to patch, read this guide: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Step 6: Flash patched boot image and reinstall Magisk for ensurance
After you pulled patched boot image from your phone, reboot your phone to fastboot mode, then execute these commands:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Note, temporarily boot method introduced back for old A/B devices like Nokia 7 Plus no longer works on Nokia 3.2 / 4.2 - it will boot your phone to Qualcomm 900E mode.
Once your phone booted to normal OS, open Magisk Manager, and reinstall Magisk and required runtime to make the root much more effective.
You may want to read this guide if you want to inherit root along with OTA update: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Extra info about custom rom:
I've tested PHH-Treble GSI on Nokia 4.2 and it made me disappointed.
The vendor compatibility is worse than FIH made Android Phones.
You may want to read this for more details: https://github.com/phhusson/treble_experimentations/wiki/Nokia-4.2
Next preview: Stock firmware reinstallation guide. Note, Nokia 3.2 / 4.2 are not made by FIH, so OST LA no longer works on both devices.
Special thanks:
@topjohnwu for Magisk
Wingtech for leaking prototype units
Reserved
not detected
my pc doesn't detect the phone when its in edl mode. before people start asking I unlocked the bootloader by enabling oem unlock in the phone settings.
I have a TA-1156 (a 3.2 variant) that has a different mainboard layout. For quite a while, I tried in vain to bring it into EDL mode - until I just tried the fastboot command "flash unlock" which worked.
I guess I should have tried that right away as I did have the OEM unlocking option in the developer setup.
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
I can enter EDL mode easily now with the patched fastboot exe. The correct driver is active and QFIL detects the phone. However, as soon as I follow the instructions by setting the programmer, and then try to start the partition manager, the phone stops responding.
After a while, I get a "sahara" error about no reply from the phone.
I wonder if someone has a stock boot.img of the Nokia 3.2 (build 00EEA) lying around ...
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JFDee said:
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
Click to expand...
Click to collapse
My guess was right. Now I'm able to reply to myself with a solution.
I tried a different prog_emmc_firehose_8937_ddr than the one provided by @hikari_calyx in the unlock thread
There is a programmer with the same name in this firmware:
sprout-015B-0-00WW-B01 .rar
It's provided by @bouyhy01 in his rooting thread.
The size of the programmer file is slightly different:
Code:
hikari_calyx: 428,936 bytes
Firmware: 428,944 bytes
Long story short: the different programmer worked in QFIL, so the partition manager worked as well, I got my own boot image, patched, flashed and had root - finally ... Thanks for all the research work, hikari_calyx and bouyhy01 !
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment prog_emmc_firehose_8937_ddr_from_fw.zip
.
JFDee said:
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
View attachment 4867461
Click to expand...
Click to collapse
I guess the only point can be connected to the ground, for example, the RF shield is grounded.
JFDee said:
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment 4869373
.
Click to expand...
Click to collapse
Thanks for info. Mine Nokia 3.2 is a prototype unit, so I don't know the situation of other versions of Nokia 3.2.
Hello, I have tried this manual for rooting Nokia 4.2 with last security update of 5th of November. After 5 step (flashing patched boot image) my phone try to reboot and then asked for factory reset (Can't load android system - Your data may be corrupt). After making factory reset there were no root at all.
What can i do next ?
PS. It's strange enough when i download boot_b image it was 63.4 Mb snd when i have patched it by Magisk manager - the size od magisk_patched.img became 10.2 Mb

Categories

Resources