Related
Hi,
I'm following the tutorial here: http://forum.xda-developers.com/showthread.php?t=1739426
I am on the 3rd option and am trying to load the latest clockworkmod on my GS3, I have it downloaded, but it is an .img file.
The tutorial says:
if you download this recovery you will need to extract this file (if you have issues extracting try removing the .md5 extension first) to get a recovery.img file and copy to your phone's internal /sdcard
connect your phone to computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
Can someone please explain this in more detail? I am looking for links to the ADB program I need as-well as how to use it to apply those commands.
Also I am having a hit-or-miss issues with Windows reading my phone as an external device, the phone reads as an established MTP connection but Windows sometimes reads it, or does not. What am I doing wrong here?
Thank you.
Info:
Phone: Samsung-SGH-I747
Carrier: AT&T
Andriod Version: 4.1.1
OS: Windows 8 64Bit
Samsung Software: Kies 2.5.0.12114_1
Here is how I done it. It's in a zip file if you already have the non-touch version installed. All you need to do with this is install from SD from CWM recovery. None of the adb stuff has to be messed with. 7th post.
http://forum.xda-developers.com/showthread.php?t=1877761
Edit: This was on down in the post you quoted. If you don't have any CWM recovery installed, then do the below, then install the above touch version zip from sd in CWM recovery.
Third, alternate #3 if unfamiliar with adb commands and uncomfortable using any command line
Decide if you want to use TWRP or CWM.
If you would like to install ClockworkMod recovery then grab Rom Manager from the Play store and in the menu select to install ClockworkMod Recovery.
I am no expert by any means but you have to run those commands in the command prompt (DOS) system. Hit the start menu and find the run and type in cmd and that will open up command line or it should be in the Accessories folder as well.
If Windows sometimes doesn't recognize your phone I would uninstall and re install the drivers to see if that helps.
I have a heck of a time to get ADB and everything working when I first started so I know how you feel. Just keep reading the forums and everything and you will get it to work.
bo.benson said:
Here is how I done it. It's in a zip file if you already have the non-touch version installed. All you need to do with this is install from SD from CWM recovery. None of the adb stuff has to be messed with. 7th post.
http://forum.xda-developers.com/showthread.php?t=1877761
Edit: This was on down in the post you quoted. If you don't have any CWM recovery installed, then do the below, then install the above touch version zip from sd in CWM recovery.
Third, alternate #3 if unfamiliar with adb commands and uncomfortable using any command line
Decide if you want to use TWRP or CWM.
If you would like to install ClockworkMod recovery then grab Rom Manager from the Play store and in the menu select to install ClockworkMod Recovery.
Click to expand...
Click to collapse
Currently my phone has NO clockwork Mod installed, I am wanting to install the latest version ( recovery-clockwork-6.0.1.2-d2att ) I have this file in .img format, I am trying to figure out how to install it on my phone -- the tutorial says add it to your sdcard, I have done that, then it says connect to your phone and use ADB commands, that is the part where I need more information, also do I wipe cache/reset settings/dalvick cache during any of this process? Should my phone be in download mode when doing ADB commands or what specifically is where I do not understand.
I would like to understand the process more in-depth and ADB as well - opposed to going the RomManager route, from my research it seems that updates/versions are available first with that method.
Thanks
Kweli87 said:
Currently my phone has NO clockwork Mod installed, I am wanting to install the latest version ( recovery-clockwork-6.0.1.2-d2att ) I have this file in .img format, I am trying to figure out how to install it on my phone -- the tutorial says add it to your sdcard, I have done that, then it says connect to your phone and use ADB commands, that is the part where I need more information, also do I wipe cache/reset settings/dalvick cache during any of this process? Should my phone be in download mode when doing ADB commands or what specifically is where I do not understand.
Thanks
Click to expand...
Click to collapse
He gave you the link to the play store app in the post. It's android terminal emulator..type terminal emulator in play store its the top app.
I just merely gave you a second option which I did and functioned flawlessly. Grab Rom Manager from the play store and select the top option to flash CWM Recovery. It will ask you your phone type and carrier and then will give you the option to install it. Easier than the whole adb thing.
Ok that route did work, thanks.
Now I installed the latest CM10 Nightly - cm-10-20121206-NIGHTLY-d2att
And then rebooted and installed the latest Gapps - gapps-jb-20121011-signed
It does not seem that any of the google apps are in my apps
Also the Play Store no longer works....just "Connection Timed Out"
Specifically I am looking to use Google Now/G-Mail/Drive/Voice/etc...
Did I do something wrong? CWM said the Gapps installed successfully. Was I supposed to wipe cache somewhere?
Thanks for the help.
bo.benson said:
He gave you the link to the play store app in the post. It's android terminal emulator..type terminal emulator in play store its the top app.
I just merely gave you a second option which I did and functioned flawlessly. Grab Rom Manager from the play store and select the top option to flash CWM Recovery. It will ask you your phone type and carrier and then will give you the option to install it. Easier than the whole adb thing.
Click to expand...
Click to collapse
Kweli87 said:
Ok that route did work, thanks.
Now I installed the latest CM10 Nightly - cm-10-20121206-NIGHTLY-d2att
And then rebooted and installed the latest Gapps - gapps-jb-20121011-signed
It does not seem that any of the google apps are in my apps
Also the Play Store no longer works....just "Connection Timed Out"
Specifically I am looking to use Google Now/G-Mail/Drive/Voice/etc...
Did I do something wrong? CWM said the Gapps installed successfully. Was I supposed to wipe cache somewhere?
Thanks for the help.
Click to expand...
Click to collapse
I have not noticed that. I used the same Gapps file to do mine and everything worked fine on I believe the 11-30 NIGHTLY, no wiping that I remember. Now this was before I got on Official JB, was still back on stock ICS. Haven't flashed CM since upgrading. I will after today as battery life sucks on the Official, if it does the same to me I will let you know.
Touch version of CWM is pretty sweet, no accidental clicks too far with the volume keys, works right from your screen. That was the link in the first post I gave you. Download it to your SD, go into recovery and install it from SD.
Looks like mine had no problems with the gapps 11-30 nightly coming from LK3. Haven't got around to downloading the latest nightly yet. Will do today. Let me know if you got it resolved.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Finally, the OTA came out. But it's still not available in my area here (Malaysia) so I have to wait for it to come. But I'm a little short of patience here, and while the OTA zip files is out, I thought I could just sideload it via adb. But when I try to make it work, I spent 4 hours facing some adb problems. I'm using Linux most of the time, and I have Android SDK downloaded. It was so troublesome to make adb work. Initially adb just couldn't find my device. So I Googled about it, and did some modifications on the PC to solve the usb problem and finally adb could connect to my device (while in Android). Then I started to follow the instructions to sideload. I booted into TWRP recovery using adb command and just to be sure, I ran ./adb devices again while the device is in recovery. But then adb shows no device connected. Trouble. I thought it's the problem with some drivers so I used Windows to try it again. Same problem again. Then I started to Google about it and found some forums that mention that it only works when I manually boot into recovery (Volume Down+Power+Volume UP). I followed. And finally, it solved it. It was only the first problem. Then I pressed into adb sideload mode in TWRP and started sideload mode. And just to be sure again, ./adb devices, no device connected again. I thought it's some bug in TWRP, I stopped sideload mode, and went back to the main menu of TWRP (where adb once can detect the device) and ./adb devices again. Guess what, it shows no device again. Problematic. I restarted my pc for many times, switching from Windows and Ubuntu for many times, repeated the above steps for many times, but the problem is just so random. I even changed the usb cable but no luck. So I decided not to use adb anymore and I've Googled for just flashing ota in TWRP. But there's just very few articles on it. Most of them are using adb and stock recovery. Some of it mentioned that if custom recovery is present then it shouldn't have to be so complicated but none of them shows how to use custom recovery. And one of them says I could just flash the OTA zip file through custom recovery but no instructions for it. The last one is my ideal method now, but because of lack of references, I'm not sure about it.
In short:
-Nexus 7 with TWRP
-problems when using adb to communicate with my device whether it's in normal boot, TWRP recovery, sideload mode, or whatever
-problem is so random and I cant figure out whats the problem
-tried installing and uninstalling and installing drivers again and again
-I dont wanna lose my data
-fed up
Question:
Is the OTA zip file recovery flashable? I dont wanna mess with adb anymore. It just wont work properly with me. Or I have to wait for OTA to reach me?
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
jj14 said:
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
Click to expand...
Click to collapse
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
ImjuzCY said:
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
Click to expand...
Click to collapse
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
jj14 said:
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
Click to expand...
Click to collapse
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
cool! (it will almost certainly require a new XPosed app because of all the changes that Lollipop brought, but it won't hurt to leave it installed)
Edit: Just read http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5 - looks like you will need to uninstall XPosed too
ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5
I have the Nokia N1. Is it there any way to install the Google Play Store (and Play Services) in it?
cisoprogressivo said:
I have the Nokia N1. Is it there any way to install the Google Play Store (and Play Services) in it?
Click to expand...
Click to collapse
haven't found a method yet so far,just wait till international version rom release
Same here. Couldn't find a way to install Play Store yet >_<
The only way for now, is either to wait for a miracle on a root method on the tablet, or wait for the official international release for their ROM.
My N1 is back into its box, as it's pretty much useless now, since over 80% of the apps these days requires Google Service Framework.
It's fine to be a MP4 player now.Install MX player, some comics reader, and some China online games. Hope official GSF come out asap.
LeignHan said:
haven't found a method yet so far
Code:
,just wait till international version rom release[/QUOTE]
I tried several times also. I noticed the model at GMC was had the chinese version info on the back of the device but was running Play Store. Tried a few versions but it exited after a breif pinwheel. The N1 device is listed on googles accepted device list pdf with no specific model information. Maybe the next version of Play store ? IDK how it works. Anyway device is not useless for me - I found most apps I require on Amazon Store or APKs. The Nokia zlaunch is excellent and waking up with screen double touch I like also. I owned apple ipad mini and prefer the build of this. Feels very sturdy - well built.
Click to expand...
Click to collapse
I also got my N1 yesterday. I tried to install the Play Store, yet no success. I also tried the method used to install it on Xiaomi devices, but the offered Play Store there is not compatible with 5.0 (permission READ_LOGS seems to be required, thus the apps crash)
I thought also about flashing the PA Gapps via the "stock" recovery. I tried following:
- Put gapps zip in /mnt/sdcard/ and renamed it to update.zip
- reboot into recovery using adb (adb works fine so far)
I hoped that the recovery would flash the zip as an update, but the error screen appeared. Knows somebody if the zip name and location are correct?
crys_ said:
I also got my N1 yesterday. I tried to install the Play Store, yet no success. I also tried the method used to install it on Xiaomi devices, but the offered Play Store there is not compatible with 5.0 (permission READ_LOGS seems to be required, thus the apps crash)
I thought also about flashing the PA Gapps via the "stock" recovery. I tried following:
- Put gapps zip in /mnt/sdcard/ and renamed it to update.zip
- reboot into recovery using adb (adb works fine so far)
I hoped that the recovery would flash the zip as an update, but the error screen appeared. Knows somebody if the zip name and location are correct?
Click to expand...
Click to collapse
I think the GAPPS zip file is not signed officially. Unless 3rd party recovery is installed, the un-signed gapps is no way to get into N1.
How did you get adb working? It doesnt seem to work for me with the Google USB drivers
EDIT: Nvm I figured it out, I needed to manually install the Google USB driver
Hello,
Has anyone of you checked if fastboot is available? Is the bootloader finally locked or not?
What have you actually checked/tested? At least could save some other guy sometime avoiding non-working retries ...
---------- Post added at 09:29 PM ---------- Previous post was at 09:19 PM ----------
Just in case it gives someone some idea. Latest nexus player came with a 64bit Atom. Could gapps be obtained from there? Just in case architecture is the problem ...
inakipaz said:
What have you actually checked/tested?
Click to expand...
Click to collapse
Okay, so I am far from an expert, here's what I found:
1. You can boot into fastboot by pressing power + vol. down when the device is off. See the attachment how it looks. I've tried a few oem commands: fastboot oem unlock, fastboot oem ?, fastboot oem command list, they don't work.
2. AFAIK there is no root method. I've tried Kingo root, others tried Root Genius, both fail to root it. Looking at chinese forums with Google translate looks like they're waiting for an international ROM with Google stuff to flash.
3. You can install Google play services. It will just crash each time something tries to use it. I've made a sample app that tries to use it, I see these exceptions in Logcat:
Code:
java.lang.SecurityException: attempting to read gservices without permission: Neither user 10060 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/com.google.android.gms.app.settings.GoogleSettingsActivity}: java.lang.SecurityException: caller uid 10060 lacks any of android.permission.INTERACT_ACROSS_USERS
java.lang.RuntimeException: Unable to create service com.google.android.gms.gcm.GcmService: java.lang.SecurityException: attempting to read gservices without permission: Neither user 10060 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
If you are interested in anything else I can try it (unless its some dangerous stuff)
Thanks syddd,
As you say i would not flash anything. I'm not an expert either.
In other ocassions a command useful to me was to boot (not flash) into custom recovery. For recovery I would try one working on similar hardware ... And from there, install superuser to root. If it is simply a clean android, that should do it.
As I said previously on other posts, I will start doing this works on mine once I got one by mid-april.
Remember, It is always important to backup current status!
As I first step I will test something like it appears on this guide for the nexus 7:
http://forum.xda-developers.com/showthread.php?t=2415668
Adapting things to similar hardware ...
Trying fastboot boot with custom recovery to know if the device is locked. If it is it should not allow this operation.
Something like method 1 in this other guide
http://forum.xda-developers.com/nexus-player/orig-development/root-google-adt-1-android-tv-t2962905
Guide on how to port CWM
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
Similar guide on twrp
http://forum.xda-developers.com/showthread.php?p=32965365#post32965365
Thanks for the guide!
I tried to follow the clockworkmod recovery one, but could not dump the boot partition. I am thinking of extracting it from the official ROM, I just dont know where those are... We could find out by snooping on the connection while the device gets a new update.
EDIT: Also "fastboot boot test.img" results in:
C:\>fastboot boot test.img
creating boot image...
creating boot image - 2048 bytes
downloading 'boot.img'...
OKAY [ 2.521s]
BUT the device does not reboot and I see the following for a split second:
"boot command stubbed in this platform!"
where test.img is just an emty file. Does this mean that the boolloader is locked?
EDIT2: I've managed to get 2 update files by clicking the "check for update" button and snooping with Wireshark what happens. It makes a POST request to http://www.fc811.com/OTA/GetOTAFirm...&fw_id=A5CN30B&serial_no=XXXXXXXX&version=1.0 , where serial_no is the serial of your device (found in the about menu) and fw_id is your current firmware. I could download 2 firmwares with this method A5CN30B and A5CN315B. Both are minor updates, if someone has the fw version from the initial release it would be useful because we could get the 5.0.2 update.
I've put these in my dropbox: https://dl.dropboxusercontent.com/u/9186429/nokia_n1/A5CN30B_update.zip https://dl.dropboxusercontent.com/u/9186429/nokia_n1/A5CN315_update.zip
Both have a droidboot.img file inside them, which is a RAMdisk boot image.
Really really nice advances!!
Thanks! You`ve been able to download I think a valid ROM for the device! Now it should be explored ...
And yes, I suppose the boot is locked which means it will not be easy to make changes.
We will need more expert hands to guide on what's next ...
In my opinion I would try to open the Image you have downloaded.
I've opened it, as you can see they are simple .zip files. But they are not ROMs. Part of them are Android patchfiles which contain just binary diffs. The bootloader is a RAMDisk which can be opened and patched with the methods you linked. The big question is whether they can be installed or not.
EDIT: see my other post, one of the older updates contains a full system image
I've been using for about 2 months. And had it repaired once, 'coz of screen issues. They sent me a new one. Very nice! Just the color changed from silver, originally, to grey, otherwise is fine.
The battery is good. It could last longer, if very much, when compared with N7.2013.LTE. The new Intel Atom looks very promising. But as you all know, there's no google play store. So I left it sleeping in the drawer.
New Play Store APK available. Just in case can anyone test it on the device?
http://forum.xda-developers.com/showthread.php?t=1996995
Hope it now works ...
It does not work.
It installs normally, but closes when I open it, just like previous versions. The problem is that play store/Google play services need some special permissions that need root. So no root = no play store.
Just need to wait for the international ROM to leak for this thing. The problem is Nokia is taking it's sweet time to release this thing anywhere else....
Here is an instruction how to install Play Store (and Play Services) on Chinese version of Nokia N1
DISCLAIMER: you're doing it on your own risk, it can probably even eat your kitten
Credits should go to rumambo who has described everything in this thread.
Original credits from rumambo:
Thanks a lot sadfrog_lin for right link
Great Thanks social-design-concepts for Tools and working solution !!!
This was successfully done by me on A5CN507 build. IMO it should work the same good on other versions of Lollipop, but I cannot promise anything.
Prerequisites
I assume that you have Intel Drivers up and running http://opensource.dell.com/releases...ition/FlashTool/IntelAndroidDrvSetup1.5.0.exe
I assume that you have adb/fastboot up and running http://forum.xda-developers.com/showthread.php?t=2317790
I assume that you have usb debugging enabled
I assume that yu have a basic knowledge how to use these tools
Installing GApps
Download GApps from this thread. I have used Nano version for Android 5.x, direct link here.
Copy it to your sdcard (any method is fine, but adb will do: adb push <filename> /sdcard/).
Download and extract IntelAndroid-FBRL-05-16-2015.7z.
Connect N1 via USB and run launcher.bat
Type ACCEPT (all capital) and select T4 method.
N1 should reboot and do a lot of things, then you should end up in temporary CWM Recovery session.
Choose install zip (volume up/down + power to select) and find and select the previously uploaded file.
After it finish reboot the tablet
Final fixes
After reboot you should have initial selection of Google Apps (including Play Store) installed. However Play Music will crash on start and GMail won't work (Play Services crashes). The reason for that is that GApps package is probably not fully prepared for x86 - but now you can simply fix it.
Go to ApkMirror and install Google Play services with -470 suffix, it is Lollipop x86 version (on the time of writing this the newest version was here ). Now both Play Music and GMail should work correctly.
An another issue is that Play Store reporting some apps (like Chrome, Google Maps, Google Earth, Chromecast, etc) as incompatible with the device. It probably could be fixed by hacking build.prop, however I haven't had time for it yet. The easiest method is to download them from ApkMirror and side install. Drawback is that you won't get autoupdates for them.
Enjoy!
reserved
reserved for a future use
For information the next update fails with this log...
I:verify_file returned 0
Installing update...
Verifying current system...failed to stat "/system/app/QuickSearchBox/QuickSearchBox.apk": No such file or directory
file "/system/app/QuickSearchBox/QuickSearchBox.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: "/system/app/QuickSearchBox/QuickSearchBox.apk" has unexpected contents.
"/system/app/QuickSearchBox/QuickSearchBox.apk" has unexpected contents.
E:Error in /cache/A5CN51C_update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
This really works! Thanks a lot.
After the installation, a few days later I found out that there was an update for N1. I could not make the update successfully. Probably the GAPP issue. So in the end, we still need the Taiwan ROM so far. So that the system update can also be made.
I installed GAPPS, but disabled root(in SuperSU's settings). I can run the OTA update (A5CN51C) successfully.
After the update, "google service is stopped" appears again. I think re-flush GAPPS and SuperSU is needed.
bricked
Hi Guys,
after the issue with the update I started replacing new files with the originals from the previous update. I've checked md5 of every file I used and compared it with update script from the new update - so I'm sure every file was correct. Actually everything was working fine with these original files.
However after the update I got a boot-loop. If I remember correctly it was something abt OpenGL in logcat. I was not able to run recovery by pressing volume up and power, but since adb was working I did it via adb. I came with an idea to clear user data. That was mistake!
Now I still have the boot-loop but developer mode was disabled by cleaning the data. My plan is to reflash with A5CN507 which contains a full system partition image. To do so I need to boot into recovery or download mode.
Do you guys have any ideas how to boot into recovery or download mode if volume up (and down) doesn't work?
Thanks in advance.
Can confirm the boot loop. I was able to get into the CMW session again and tried to restore the backup I made before installing the gapps but CMW got stuck while restoring the system partition.
The device is now stuck in the "Powerd by Android" screen, any help is warmly welcome
Can't root by the method after update to latest 5.1.1 firmware. Pls update the method
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Ahbrosha said:
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Click to expand...
Click to collapse
Your tablet bootloader is locked by the update. I've not found any ways to unlock it and install google play.
same here 5.1.1 messed everything up
Ahbrosha said:
After the update to 5.1.1 I get an error from the Play Services: Wrong archticture ( x86, x86_64). Does anyone know were I can get a APK for the x86_64 Play Services?
Click to expand...
Click to collapse
same here - so I thought I redo the whole thing with Gapps for 5.1.1, but now Fastboot Tethered Recovery Launcher doesn't recongnize my N1 anymore. Can anybody help? Thanks in advance
Any chance that the following common command work ?
Code:
fastboot oem unlock
jujudeshighlands said:
Any chance that the following common command work ?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
It's used to make your device unlocked, but only limited to some devices.
http://lifehacker.com/the-most-useful-things-you-can-do-with-adb-and-fastboot-1590337225
jujudeshighlands said:
Any chance that the following common command work ?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thank you,
I tried that, it didn't work - it says "waiting for device", but it waits forever. As to the Fastboot Tethered recovery launcher, this time I used the one from Jul, 27, before I had an earlier version. Could it be that the older version would work, but not the latest one? It does recognize my device, but it says unauthorized, although it OEM-unlocked and USB debugging is authorized. Thanks for any help.
and that's the end of it, good night N1
Since my N1 is still bricked, hung halfway through bootloading, I talked to an Android-Repair-shop. They said it cannot be unbricked, I would need a new motherboard... but motherboards for the N1 are not available.
Does anyone hv better news?
Hi,
so I came back to the problem today - and I managed to unbrick my device. Somehow (vol-up + power) I managed to enter fastboot. Then I rebooted into recovery and sideloaded a full update.zip with 701.
Now I'm trying to change Chinese version to Taiwanese one.
my nokia n1 stuck
my Nokia n1 stuck at boot screen i lost my recovery too my tablet only open at fastboot mode.Pls HELP
i need boot.img and recovery.img for NOKIA N1(A5CNS1C)
Good day. What are the opportunities to put Google play on version 5.1.1 ?Bought and it came with this version.A5CNB19
sasha2910 said:
Good day. What are the opportunities to put Google play on version 5.1.1 ?Bought and it came with this version.A5CNB19
Click to expand...
Click to collapse
I will be posting a complete guide about Google play store for your Chinese Nokia n1. Tried different methods and finally got it right. Keep waiting...
LineArc said:
I will be posting a complete guide about Google play store for your Chinese Nokia n1. Tried different methods and finally got it right. Keep waiting...
Click to expand...
Click to collapse
Can't wait for that! :good::good::good::good::good::good:
Everything you do, you do at your own risk. I'm not responsible for all damages, this can also lead to loss of warranty.
Hi,
Probably many of you know how to do a Magisk install without TWRP, but this guide is for people who don't know and don't want to mess things up.
I will try to show you step by step how to do it.
Many thanks to:
kdrag0n
topjohnwu
Leave them a nice feedback
!!! Before we start make sure your device is unlocked, if you don't know how to do it below is link to official Xiaomi guide !!!
https://c.mi.com/thread-2262302-1-0.html
Requirement
Xiaomi Mi Flash ver. =>3-14-0 - Needed to install all adb drivers Download
ADB & Fastboot tools - Could be the one built into Mi Flash tool I'll use this to make it simple
Magisk =>24.2 - This software is base of our rooting process Download
SafetyNet Fix => 2.2.1 (Zygisk) - Needed to backdoor SafetyNet fail check, at the moment it is only working method for Mi Pad 5 Download Make sure you download the Zygisk version!
Boot.img - You can download from official MIUI website full flashable rom and separate boot.img file from there, or use my if your Miui version is China 13.0.5, EEA 13.0.3, Global 13.0.1
China 13.0.5EEA 13.0.3Global 13.0.1Installation
To make it easier, Green color mean what you need to do on Tablet, Orange on PC
Unzip Mi Flash tool
Open folder and run XiaoMiFlash.exe, if window "Driver" won't pop-up click on the Driver tab and then "Install" button and close all windows.
Connect your tablet to computer, when your tablet ask how you want use USB, choose File Transfer/Android Auto
Copy to internal storage Magisk-v****.apk, safetynet-fix-v****.zip and boot.img
Open File Manager on your tablet find a folder where you copied all files, and install Magisk
Open Magisk app, and click on Install in section Magisk, then select "Select and Path a File", after that find your boot.img file and click on it
Click "LET'S GO" button on the right side and wait until process will be finished
On your computer in the tablet's storage window, go to the file specified in the application probably /Download/magisk_patched-*****
Copy this file to a subfolder of Mi Flash on your computer, exactly to MiFlash2020-3-14-0\Source\ThirdParty\Google\Android and change the name of this file to boot.img
Open PowerShell/Windows Terminal in this folder (Hold Shift + Right click -> Open PowerShell window here)
Make sure your tablet have enabled USB debugging in Developer options Setting -> Additional settings -> Developer options -> USB debugging
Turn off your tablet, then hold down Power and VOL- until the screen lights up, then release power button, if Fastboot appears, everything went fine
Go back to your Terminal window and type to check if your computer see your tablet
Code:
./fastboot.exe devices
If you see answer "******** fastboot" it mean there is communication between PC and Tablet
Next type this command to flash patched boot image
Code:
./fastboot.exe flash boot boot.img
Next type this command to reboot your device
Code:
./fastboot.exe reboot
Restart can take a longer time than normal
Open Magisk app and check status of Magisk, if you see for exaple "Installed 24.2 (24200)" everything went fine
Open Settings in right corner of app and in section App click on Hide the Magisk app then type name for hidden app, it will ask to install new app so do it
Open again Magisk app and open Settings in section Magisk enable Zygisk (Beta) and Enforce DenyList
Click on Configure DenyList than click on three dots in right corner and uncheck Show system apps
Search for all the apps in the list below and check them. It is important to click on their name to see all modules, once you have done this click on the box to activate all of them
Code:
Google
Google Assistant (I have two)
Google Pay
Google Play services
Google Play Store
After that reboot your tablet, and open again Magisk app
On the bottom click on Modules
Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
After that reboot your device one more time
After reboot open Android Settings go to Apps and Unhide system services than find and clear all data of Google Play services and Google Play Store
Reboot tablet last time
If you have reached this point it means that everything has gone correctly, probably for about 3 hours you will still not be able to install Netflix and some banking applications but after this time everything will be back to normal, this is because Google's servers have detected that Magisk has been installed but that the application has been changed and Zygisk has been enabled so at the next check it notices that everything is Ok and gives access back.
Quick explaination what happend here:
Magisk has been installed and device is Rooted
The application has been changed and hidden
Zygisk has been activated and hidden from Google services
SafetyNet-fix was installed, which restores the functionality of SafetyNet and Widevine L1, which is blocked after the installation of Magisk and unlocked Bootloader
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Nux01 said:
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Click to expand...
Click to collapse
Hi Nux01,
1. Unfortunately yes, TWRP isn't supported for Pad 5 yet.
2. It won't work, TWRP app is only making a request to TWRP custom recovery, until it doesn't exist you can't even install custom ROM
3. It is, but i didn't test it yet on Pad 5, and I don't know if it will work with new decides because last release is from 20.07.2020.
https://github.com/francescotescari/XiaoMiToolV2/releases
4. Yes, you need Xiaomi account, also your device has to be logged in, and registered to unlock, Xiaomi made complete guide how to do this, link is on the top of this post.
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Nux01 said:
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Click to expand...
Click to collapse
I mean it's quite old release so it may not work with current unlock bootloader process on new devices like a Xiaomi 12, Xiaomi Pad 5 etc. I can't promise it won't brick your device, only confirmed method is by official Xiaomi tool.
Thank you
I'll wait a little bit before rooting my tablet.
Have a nice day.
Followed the instruction, worked like a charm. Although I had unknown "chinese sings" errors with the driver install it worked. By the way there is a newer version of the flashing tool.
Thanks for the effort of writing this down!
Hello,
I just managed to unlock the bootloader of my tablet "Pad 5".
I tried under Mac and Linux with Xiaomitool V2 without success (error 20036 and 20045).
I also tried with VirtualBox who did not recognize the tablet.
I succeeded with VMware and Windows 7 by testing different drivers and it worked.
I just root the tablet with Magisk.
On the other hand, is there the equivalent of TWRP to make a complete system backup. Apart from Titanium and MyBackup.
Thanks for your help.
thanks dude.
didn't try this yet, just wondering.
can't i just flash recovery and then flash magisk.apk?
thanks
Can i update ota to 13.0.2 after rooted? Just update and root again?
Cpanel10x said:
Can i update ota to 13.0.2 after rooted? Just update and root again?
Click to expand...
Click to collapse
You can update, but after that you need root again but with boot.img from 13.0.2
How to get the boot.img 13.0.2? I checked the 3GB Firmware and only found vendor_boot.img. Is it the same thing?
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Thomas Brown 99 said:
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Click to expand...
Click to collapse
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Thanks for this awesome guide. Do you have some suggest about the magisk modules to install?
thanks, it just worked perfectly and your step by step guide is very handy and helpful. thanks so so much.
vjsaini00 said:
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Click to expand...
Click to collapse
Today evening, I'll add more boot.img
kisielec said:
Today evening, I'll add more boot.img
Click to expand...
Click to collapse
eagerly waiting, Thanks
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
24. Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
25. After that reboot your device one more time
Click to expand...
Click to collapse
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
cysmaster said:
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
Click to expand...
Click to collapse
I also have this module installed without problems, as there is no recovey for Pad5, it is a good idea to install in magisk the module Magisk Bootloop Protector, which serves exactly to prevent what you are afraid that happen with your tablet