Related
just done a full sbf flash to 1.8.3 and then the puddin sbf and now i am getting
Code:
C:\adb>moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
sending 'boot' (3358 KB)... OKAY [ 0.263s]
writing 'boot'... OKAY [ 0.551s]
C:\adb>moto-fastboot flash system atrix-2.3.4-hktw-system.img
sending 'system' (262144 KB)... OKAY [ 20.649s]
writing 'system'... OKAY [ 13.953s]
sending 'system' (65410 KB)... OKAY [ 5.071s]
writing 'system'... OKAY [ 3.469s]
C:\adb>moto-fastboot flash webtop atrix-2.3.4-hktw-webtop.img
load_file: could not allocate 805177344 bytes
error: cannot load 'atrix-2.3.4-hktw-webtop.img'
C:\adb>moto-fastboot flash recovery recovery-en-goapk-0625-2034.img
sending 'recovery' (4598 KB)... OKAY [ 0.370s]
writing 'recovery'... OKAY [ 0.665s]
C:\adb>
I think my webtop partition is corrupted... I was trying to send the update zip from this thread to my sdcard from adb by using adb push Navalynt_HKTW_v1.7_webtop.zip /sdcard-ext/Navalynt_HKTW_v1.7_webtop.zip and itt sat there for a long time so i unplugged the usb cable. since then this was happening. I can still run GB 2.3.4 and 1.8.3 but for some reason I can't flash the webtop partition
I'm not sure when come from the error but it looks like your computer or may be your phone don't have enought memory to allocate (for the flash process).
That's funny because I've done it before when it was first leaked. i'm not sure what's going on
Seriously? am I the only one this happened to?
SolidHelix said:
error: cannot load 'atrix-2.3.4-hktw-webtop.img'
Click to expand...
Click to collapse
If you look at that error, it looks like its looking for another file named "atrix-2.3.4-hktw-webtop.img"
SolidHelix said:
and itt sat there for a long time so i unplugged the usb cable. since then this was happening.
Click to expand...
Click to collapse
From the Developers post:
**DOWNLOAD v1.7a HERE (WITH Webtop fix)**
*Please ignore that when the script runs it still says v1.6, it's really v1.7 I just forgot to update that line before uploading!
FYI -The Webtop takes a few minutes to install ... so once you start flashing the zip let it be a few minutes (it's working, not frozen)!
SolidHelix said:
Seriously? am I the only one this happened to?
Click to expand...
Click to collapse
Dude chill out. Its only been a hour since you posted. Check back in a day or two.
If you look at that error, it looks like its looking for another file named "atrix-2.3.4-hktw-webtop.img"
Click to expand...
Click to collapse
Isn't that the file I'm attemting to flash?
From the Developers post:
**DOWNLOAD v1.7a HERE (WITH Webtop fix)**
*Please ignore that when the script runs it still says v1.6, it's really v1.7 I just forgot to update that line before uploading!
FYI -The Webtop takes a few minutes to install ... so once you start flashing the zip let it be a few minutes (it's working, not frozen)!
Click to expand...
Click to collapse
I don't think you are following.. I didn't pull the plug while flashing this update in CWM. I was in CWM and connected via adb and typed command adb push Navalynt_HKTW_v1.7_webtop.zip /sdcard-ext/Navalynt_HKTW_v1.7_webtop.zip to load the zip onto my sd-card so that I COULD flash it with cwm. rather than booting up my phone and copying via usb host. I'm after installing this zip I know it takes a while to get past the webtop part.
anyway I still can't see why I can't flash the webtop partition. I have done so several times since the bootloader got unlocked.
Dude chill out. Its only been a hour since you posted. Check back in a day or two.
Click to expand...
Click to collapse
Agreed
bump..... obviously not gonna get any help here pushed to the second page with no replies... guess i'll have to get flamesd for bringing it to the development section
Just want to say, I found the problem.. It was my USB 3.0 port. ****ty Asus drivers, it never worked right. copying large files cause it to fail. Who would have thought? Oh well back to normal.
btw
THANKS FOR THE SUPPORT EVERYONE!!!
just kidding... no one could help me with that one
Interesting, I have the same problem.
Not sure if this could have fixed it too.
I flashed CG58.SMG from 1.8.3 sbf. That is the webtop original webtop image from 1.8.3. I used depacker to split the 1.8.3 sbf into smg files, found CG58.smg and renamed to CG58.IMG and flashed with mot-fastboot. The thing is, when it fixed i was flashing from a different computer so that's why figured it was the USB that was the problem
Download depacker 1.3 here
Open 1.8.3 sbf with it and click split
browse to the folder it created and find CG58,smg and rename to CG58.img
put img in same dir as moto-fastboot
in cmd promt run moto-fastboot flash webtop CG58.img
Like I said I'm not sure it was this that fixed it or the fact that I flashed from a different computer this time
Sent from my MB860 using XDA Premium App
Yeah, did what you did with the depacker, still having same problem. I am guessing it is the usb drivers. I tried using flash_image script from cyanogen mod, but that spits out a syntax error(great...). I am gonna try to rewrite the mmcblk0p13 partition with the dd command, is that the same as flashing?
I should ask tenfar if he can add an option to backup/restore/flash /osh to cwm. That would be nice.
Hi guys,
I searched but couldn't find any applicable matches (all rooted devices or the solutions didn't work for me)
I have a stock, unrooted Nexus 10 (UK). My wife used it one night while I was out and now it won't boot past Google logo! Pretty sure it's nothing she's done as she would have only been playing games on it and I have avg antivirus and lookout antivirus (think it's called something else now) and disallowing apps to be installed from third parties... Even so when I try to boot it sits on Google logo permanently (left it over an hour and it gets no further...)
I can get into boot loader mode and select recovery mode but all this does is reboot to the Google logo forever more.
It does this when not connected to PC and when it is connected
Downloaded the drivers from Samsung US website but when windows vista looks for drivers and I point it at the folder the drivers are installed to it finds nothing
I'm thinking (/hoping) maybe it's just the wrong drivers preventing recovery mode from working but any help would be greatly appreciated
Sam.
Update:
Managed to find the right drivers from Google in the end, but I still can't get recovery mode to work - just sits on the Google logo still
any help at all would be great...
Sam.
samyoue said:
Hi guys,
I searched but couldn't find any applicable matches (all rooted devices or the solutions didn't work for me)
I have a stock, unrooted Nexus 10 (UK). My wife used it one night while I was out and now it won't boot past Google logo! Pretty sure it's nothing she's done as she would have only been playing games on it and I have avg antivirus and lookout antivirus (think it's called something else now) and disallowing apps to be installed from third parties... Even so when I try to boot it sits on Google logo permanently (left it over an hour and it gets no further...)
I can get into boot loader mode and select recovery mode but all this does is reboot to the Google logo forever more.
It does this when not connected to PC and when it is connected
Downloaded the drivers from Samsung US website but when windows vista looks for drivers and I point it at the folder the drivers are installed to it finds nothing
I'm thinking (/hoping) maybe it's just the wrong drivers preventing recovery mode from working but any help would be greatly appreciated
Sam.
Click to expand...
Click to collapse
Ok, can you put your tablet in fastboot and can your PC see you tablet in fastboot?? What is your PC's OS?
Hi!
Thanks for replying
I've held down all 3 buttons and get a different to normal screen where I can select "start now" "power off" and "recovery mode", is this fast boot? If not how do I get to fast boot? When it's on the screen mentioned above my laptop (running vista 32 bit) started looking for drivers and I pointed it at the nexus ones I downloaded and it installed successfully... Hope this helps I'm well out side my experience here! Programming from within a desktop environment is no problem for me but tinkering with booting and stuff is all new to me :-s
Cheers!
samyoue said:
Hi!
Thanks for replying
I've held down all 3 buttons and get a different to normal screen where I can select "start now" "power off" and "recovery mode", is this fast boot? If not how do I get to fast boot? When it's on the screen mentioned above my laptop (running vista 32 bit) started looking for drivers and I pointed it at the nexus ones I downloaded and it installed successfully... Hope this helps I'm well out side my experience here! Programming from within a desktop environment is no problem for me but tinkering with booting and stuff is all new to me :-s
Cheers!
Click to expand...
Click to collapse
Ok you need the fastboot.exe and the adb.exe in the root of your c drive... When you get them in there just search google you will find them... They should come as a zip not a exe and they are not installable they are just executable from CMD window... Than open your CMD window as ADMIN.... Than type
Code:
cd /
That will get you to the root of your c drive
Once there
To verify that your exe's are in the right place type
Code:
dir
This will list the contains of root of your c drive make sure you can see the exe's
Than type
Code:
fastboot
If you get a list of commands your golden !!!!!!
Boot your tablet in that mode you talked about and dont do anything just plug it in to your PC
than type
Code:
fastboot devices
Let me know when you get there and if you have any questions you have along the way.....
THx lj
That's excellent help thank you
Yup I got list of commands, then connected Tablet into boot loader (?) mode and typed fastboot devices and got the following :
Code:
C:\>fastboot devices
R32D203TBBR fastboot
C:\>
What now?
samyoue said:
That's excellent help thank you
Yup I got list of commands, then connected Tablet into boot loader (?) mode and typed fastboot devices and got the following :
Code:
C:\>fastboot devices
R32D203TBBR fastboot
C:\>
What now?
Click to expand...
Click to collapse
Yes!!!!!!!!!!!!!
---------- Post added at 01:24 PM ---------- Previous post was at 01:19 PM ----------
Go here https://developers.google.com/android/nexus/images
The nexus 10 code name is 'mantaray' MAKE SURE YOU GET THE RIGHT ONE......
Get the verison you would like......
Than on the downloaded directory do a....
Code:
dir
So I can see whats in there....
inside the tgz file was a tar file, inside that was:
Code:
C:\nexus\mantaray-kot49h-factory-174ba74f\mantaray-kot49h-factory-174ba74f\manta
ray-kot49h>dir
Volume in drive C is Vista
Volume Serial Number is 98A3-557B
Directory of C:\nexus\mantaray-kot49h-factory-174ba74f\mantaray-kot49h-factory-
174ba74f\mantaray-kot49h
02/03/2014 22:28 <DIR> .
02/03/2014 22:28 <DIR> ..
09/12/2013 23:31 1,310,720 bootloader-manta-mantamf01.img
09/12/2013 23:31 968 flash-all.bat
09/12/2013 23:31 856 flash-all.sh
09/12/2013 23:31 700 flash-base.sh
09/12/2013 23:31 394,876,070 image-mantaray-kot49h.zip
5 File(s) 396,189,314 bytes
2 Dir(s) 18,853,072,896 bytes free
and inside the zip file is:
Code:
C:\nexus\mantaray-kot49h-factory-174ba74f\mantaray-kot49h-factory-174ba74f\manta
ray-kot49h\image-mantaray-kot49h>dir
Volume in drive C is Vista
Volume Serial Number is 98A3-557B
Directory of C:\nexus\mantaray-kot49h-factory-174ba74f\mantaray-kot49h-factory-
174ba74f\mantaray-kot49h\image-mantaray-kot49h
02/03/2014 22:34 <DIR> .
02/03/2014 22:34 <DIR> ..
04/12/2013 15:38 57 android-info.txt
01/01/2009 00:00 4,898,816 boot.img
04/12/2013 16:13 10,621,244 cache.img
01/01/2009 00:00 5,462,016 recovery.img
01/01/2009 00:00 662,821,052 system.img
04/12/2013 16:13 140,778,452 userdata.img
6 File(s) 824,581,637 bytes
2 Dir(s) 18,025,598,976 bytes free
I'm guessing we are going to reinstall the factory OS version 4.4.2 (what it was previously i think...) or should i get earlier version of 4.4?
Can't wait!
thanks again for all your help so far
EDIT:- PS just in case, the info on the bootloader screen
Code:
DEVICE INFORMATION
PRODUCT NAME: manta
VARIANT: wifi
H/W VERSION: 8
BOOTLOADER VERSION: MANTAMF01
CARRIER INFO: NONE
SERIAL NUMBER: R32D203TBBR
LOCK STATE: LOCKED
REBOOT MODE FLAG: NONE
samyoue said:
inside the tgz file was a tar file, inside that was:
Code:
C:\nexus\mantaray-kot49h-factory-174ba74f\mantaray-kot49h-factory-174ba74f\manta
ray-kot49h>dir
Volume in drive C is Vista
Volume Serial Number is 98A3-557B
Directory of C:\nexus\mantaray-kot49h-factory-174ba74f\mantaray-kot49h-factory-
174ba74f\mantaray-kot49h
02/03/2014 22:28 <DIR> .
02/03/2014 22:28 <DIR> ..
09/12/2013 23:31 1,310,720 bootloader-manta-mantamf01.img
09/12/2013 23:31 968 flash-all.bat
09/12/2013 23:31 856 flash-all.sh
09/12/2013 23:31 700 flash-base.sh
09/12/2013 23:31 394,876,070 image-mantaray-kot49h.zip
5 File(s) 396,189,314 bytes
2 Dir(s) 18,853,072,896 bytes free
and inside the zip file is:
Code:
C:\nexus\mantaray-kot49h-factory-174ba74f\mantaray-kot49h-factory-174ba74f\manta
ray-kot49h\image-mantaray-kot49h>dir
Volume in drive C is Vista
Volume Serial Number is 98A3-557B
Directory of C:\nexus\mantaray-kot49h-factory-174ba74f\mantaray-kot49h-factory-
174ba74f\mantaray-kot49h\image-mantaray-kot49h
02/03/2014 22:34 <DIR> .
02/03/2014 22:34 <DIR> ..
04/12/2013 15:38 57 android-info.txt
01/01/2009 00:00 4,898,816 boot.img
04/12/2013 16:13 10,621,244 cache.img
01/01/2009 00:00 5,462,016 recovery.img
01/01/2009 00:00 662,821,052 system.img
04/12/2013 16:13 140,778,452 userdata.img
6 File(s) 824,581,637 bytes
2 Dir(s) 18,025,598,976 bytes free
I'm guessing we are going to reinstall the factory OS version 4.4.2 (what it was previously i think...) or should i get earlier version of 4.4?
Can't wait!
thanks again for all your help so far
EDIT:- PS just in case, the info on the bootloader screen
Code:
DEVICE INFORMATION
PRODUCT NAME: manta
VARIANT: wifi
H/W VERSION: 8
BOOTLOADER VERSION: MANTAMF01
CARRIER INFO: NONE
SERIAL NUMBER: R32D203TBBR
LOCK STATE: LOCKED
REBOOT MODE FLAG: NONE
Click to expand...
Click to collapse
Move these 3 files make sure the zip is still zipped up!!!! To the root of your c drive
Code:
09/12/2013 23:31 1,310,720 bootloader-manta-mantamf01.img
09/12/2013 23:31 968 flash-all.bat
09/12/2013 23:31 394,876,070 image-mantaray-kot49h.zip
Put your tablet into fastboot, make sure you can see your device on your PC with
Code:
fastboot devices
if you get the numbers than run this command and the script will do it all for you.....
Code:
flash-all.bat
Let me know if you have any questions... Thx as always lj
I followed your instruction and I got up to the part where it say
sending 'system' (647286 KB) ...
and it just hang.
on the nexus 10, it shows
fastboot status data2781d8bc
any idea?
lmfaznboi said:
I followed your instruction and I got up to the part where it say
sending 'system' (647286 KB) ...
and it just hang.
on the nexus 10, it shows
fastboot status data2781d8bc
any idea?
Click to expand...
Click to collapse
I guess to write the data we need to unlock your bootloader but no worries, once done you can just lock it back up as long as you flash
a stock firmware package....
So enter fastboot make sure you can see you tablet from your pc than type
Code:
fastboot oem unlock
Than it will just say your going to lose your data...Ok than it will do its thing.....
Than run the flash-all.bat
than boot fully into stock rom
than reboot into fastboot
and lock your bootloader with.... If thats is what you want to do....
Code:
fastboot oem lock
Let me know if this helps you
yes i had to unlock first but...
I HAVE MY NEXUS BACK!!!! WOOHOO!!
now to spend next few weeks setting it up how I want again lol that'll teach me not to back stuff up!
thank you sooo so much for all your help lj - you're a superstar genius!!
samyoue said:
yes i had to unlock first but...
I HAVE MY NEXUS BACK!!!! WOOHOO!!
now to spend next few weeks setting it up how I want again lol that'll teach me not to back stuff up!
thank you sooo so much for all your help lj - you're a superstar genius!!
Click to expand...
Click to collapse
GREAT !!!! To see it up and running for you... Happy setting her up !!!! If you ever need any other help just drop me a line... Thx as always lj
lj50036 said:
GREAT !!!! To see it up and running for you... Happy setting her up !!!! If you ever need any other help just drop me a line... Thx as always lj
Click to expand...
Click to collapse
its still not working. I did what you told me, my nexus already unlocked. so I relock it and unlock again. and now it stuck at sendind 'bootloader' (1280)
and on my nexus it shows.
fastboot status - Data0014000
lmfaznboi said:
its still not working. I did what you told me, my nexus already unlocked. so I relock it and unlock again. and now it stuck at sendind 'bootloader' (1280)
and on my nexus it shows.
fastboot status - Data0014000
Click to expand...
Click to collapse
Copy and paste the whole command input and output.....
lj50036 said:
Copy and paste the whole command input and output.....
Click to expand...
Click to collapse
C:\AndroidSDK\tools>flash-all.bat
erasing 'boot'... OKAY
erasing 'cache'... OKAY
erasing 'recovery'... OKAY
erasing 'system'... OKAY
erasing 'userdata'... OKAY
sending 'bootloader' (1280 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32CB03FJZT
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (4784 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (5334 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (647286 KB)...
it still stuck at the system. I managed to get pass the bootloader phase.
lmfaznboi said:
C:\AndroidSDK\tools>flash-all.bat
erasing 'boot'... OKAY
erasing 'cache'... OKAY
erasing 'recovery'... OKAY
erasing 'system'... OKAY
erasing 'userdata'... OKAY
sending 'bootloader' (1280 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32CB03FJZT
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (4784 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (5334 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (647286 KB)...
it still stuck at the system. I managed to get pass the bootloader phase.
Click to expand...
Click to collapse
Try a different usb cable or a different usb port.....
Or try flashing them separately
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Or try flashing them separately
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No a bad idea @demkantor maybe just run these before you flash them individually...
Code:
fastboot erase system
fastboot erase recovery
fastboot -w
fastboot erase boot
fastboot erase misc
fastboot erase cache
Just what I would do if it were mine.....
lj50036 said:
No a bad idea @demkantor maybe just run these before you flash them individually...
Code:
fastboot erase system
fastboot erase recovery
fastboot -w
fastboot erase boot
fastboot erase misc
fastboot erase cache
Just what I would do if it were mine.....
Click to expand...
Click to collapse
I think its the cable, since I lost my orginal cable and using my logitech cable that came with my mouse. but ill try flashing them individually and see how i goes. I already ordered an oem cable and should come next week.
While Flashing Rom, Kernel, OR Downgrading Android. We often Brick our Devices, But using this Guide you can actually Revive your Hard Bricked Yureka OR Yureka Plus.
I personally Revived my Yureka by following these steps, If you can't Revive it, so check somewhere you are going Wrong.
This is a Complete and Shortened Guide to Unbrick Yureka or Yureka Plus.
Credits:
1) @tirta.agung
2) @Jimmyz0r
3) @Diwakar1990
Symptoms 1 for Hard Bricked Yureka:
1) No LED when Charger/Data Plugged.
2) Continuous Vibration.
3) No Response/Vibration from Device when Pressing any Power+Volume Combination.
(If you are facing same, So you will definitely be able to Unbrick your Device, But IMEI will be vanished, you can later recover it by using QXDM, QPST.)
Symptoms 2 for Hard Bricked Yureka:
1) LED lights when charger/data Plugged.
2) No Boot Image, No Recovery, No Fastboot.
3) No Vibration.
(Even in this condition, you will definitely Unbrick your Device, your IMEI is still safe, But can't guarantee, it depends on which partition you played with.)
Symptom 3 for Hard Bricked Yureka:
1) Vertical Lines on Display which brightens slowly, as soon as you Power On your Yureka.
(This is the easiest method, Just flash Proper Fastboot Files, and your Yureka will be alive.)
Things which you will need:
1) Computer.
2) Minimum 16 GB Memory Card.
3) Win32DiskManager
4) eMMC Storage of Yureka. (Click Here) CRDTS: [email protected]
5) Screw Driver, to Open all Screws at back. (I'm not responsible for any Damage or Warranty related Issues.)
6) Small Copper Wire.
7) Yureka Fastboot Images. (Click Here) (I understand, most of them who bricked their Device belongs to Developer Community, Flashing Rom&Kernel is usual for them so they have Fastboot Images, But Please Download Fastboot Images and Fastboot Package which I've provided in Links.)
8) Fastboot Flashing Package. (Click Here)
9) Download ADB Drivers, the best way to install ADB Drivers is Install PDANET in your computer. (Download PDA Net)
9) It is little Difficult for a Noob to follow these steps, But not Impossible. Pay attention to each and every steps.
Steps for Symptoms 1 and 2.
1) Making a Memory Card Burnt with eMMC Files.
a) Extract the eMMC file of Yureka (backup.zip), after extracting it will be converted to approx 14 GB (Magic
b) Connect your 16 GB memory Card to Computer with a Card Reader.
c) Open Win32DiskManager, Select the extracted .img File and click on Write. the flashing process will start. (Just confirm the Disk Letter of your Card Reader before burning, otherwise it can lead to a severe damage to any partition of your hard disk.)
d) After Process completes, Disconnect Card Reader and keep the memory Card.
2) Removing All Screws and How to use small copper Wire.
(Hardware Repairing is Easier than Software Repairing, so don't Panic)
a) After Removing All Screws Open the White Panel.
b) On Top Right Side (near Headphone Socket) you will see 6 Dots.
c) Tap and hold 2nd Dot with the 6th Dot using a small Copper Wire.
To make it more clear check the Images.
{
"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"
}
3) Actual Flashing Process.
a) Extract Fastboot Package.
b) Extract Fastboot Rom inside Fastboot Package.
c) Insert Burnt Memory Card in Yureka.
d) Plug the Battery.
e) Tap and Hold 2nd and 6th Dot using copper wire as shown in Picture.
f) Press and Hold Volume Up Button.
g) And All together connect Data Cable from Computer to Yureka. (I required Second person, It is very difficult to do it all together.)
h) Right Click on Start, Open Device Manager, It will show Android Phone at first.
Congratulations, you are now in Fastboot Mode.
(If there is an exclamation near Android Phone, means your Drivers are not installed, Install PDA NET, check at Top in Requirements.)
If you are not able to boot in Fastboot Mode, try these steps again and again.
i) Open the Folder where you have extracted Fastboot Package and the whole Rom File.
j) Double Click on FlashAll.bat.
After Flashing Process is done, your Device will normally Boot.
Symptom Number 3:
Vertical Lines which Brightens slowly.
Fastboot Mode is working in this situation, Just flash Proper Packages and your Device will be Alive.
1) Yureka Fastboot Images. (Click Here)
2) Yureka Fastboot Package. Fastboot Flashing Package. (Click Here)
3) Install ADB Drivers in Computer. (Download PDA Net)
4) Remove the Battery for 5-10 Seconds, Insert it again
5) Press and Hold Volume Up Button, Plug Data Cable.
6) Open Device Manager and Check your Device. (Optional).
7) Extract Yureka Fastboot Package, Extract Yureka Fastboot Images inside Yureka Fastboot Package extracted folder.
8) Double Click on FlashAll.bat.
9) Wait for process to complete, and your device will Reboot.
how much memory does a 16 gb memory exactly have...
Great tutorials broo
Thanks @naved97 can you tell me where we are using 16gb mc in the whole process???
---------- Post added at 04:36 AM ---------- Previous post was at 04:23 AM ----------
Please help im getting write failure. While using flash_all.bat. Below is the log.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash_all.bat
---------------------[ Start flashing ROM ]-------------------------
----------------[ Checking for connected devices ]------------------
---------------[ Flashing modem and bootloader ]--------------------
< waiting for device >
target reported max download size of 268435456 bytes
sending 'aboot' (3871 KB)...
OKAY [ 0.133s]
writing 'aboot'...
FAILED (remote: device is locked)
finished. total time: 0.136s
target reported max download size of 268435456 bytes
sending 'hyp' (72 KB)...
OKAY [ 0.005s]
writing 'hyp'...
FAILED (remote: device is locked)
finished. total time: 0.011s
target reported max download size of 268435456 bytes
sending 'modem' (46209 KB)...
OKAY [ 1.635s]
writing 'modem'...
FAILED (remote: device is locked)
finished. total time: 1.639s
target reported max download size of 268435456 bytes
sending 'rpm' (150 KB)...
OKAY [ 0.008s]
writing 'rpm'...
FAILED (remote: device is locked)
finished. total time: 0.010s
target reported max download size of 268435456 bytes
sending 'sbl1' (276 KB)...
OKAY [ 0.012s]
writing 'sbl1'...
FAILED (remote: device is locked)
finished. total time: 0.019s
target reported max download size of 268435456 bytes
sending 'tz' (496 KB)...
OKAY [ 0.019s]
writing 'tz'...
FAILED (remote: device is locked)
finished. total time: 0.024s
---------------------[ Rebooting into new bootloader ]-----------------------
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
------------[ Waiting for device to reboot into bootloader ]-------------------
Waiting for device to reboot into bootloader...
-------------------[ Unlocking bootloader ]-------------------------
...
(bootloader) Warning: unlock will wipe all user data
(bootloader) Press Volume Up key to confirm
(bootloader) Press Volume Down key to cancel
(bootloader) Erasing userdata.
OKAY [ 3.798s]
finished. total time: 3.799s
----------------------[ Flashing kernel ]---------------------------
target reported max download size of 268435456 bytes
sending 'boot' (16792 KB)...
OKAY [ 0.567s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.619s
----------------------[ Flashing recovery ]-------------------------
target reported max download size of 268435456 bytes
sending 'recovery' (19670 KB)...
OKAY [ 0.659s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.674s
-------------------[ Flashing cache partition ]---------------------
error: cannot load 'cache.img'
-------------------[ Flashing userdata partition ]---------------------
target reported max download size of 268435456 bytes
erasing 'userdata'...
OKAY [ 0.057s]
sending 'userdata' (137274 KB)...
OKAY [ 4.555s]
writing 'userdata'...
FAILED (remote: flash write failure)
finished. total time: 4.626s
-------------------[ Flashing system partition ]--------------------
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.021s]
sending sparse 'system' (259912 KB)...
OKAY [ 11.923s]
writing 'system'...
OKAY [ 2.917s]
sending sparse 'system' (257987 KB)...
OKAY [ 12.225s]
writing 'system'...
FAILED (remote: flash write failure)
finished. total time: 27.153s
---------------------[ Rebooting device ]---------------------------
rebooting...
finished. total time: 0.003s
-------------------------[ ALL DONE ]-------------------------------
AO5510 backup file missing
plz give the ink for ao5510 backup.zip file its link was expire
RELAX and 100% Unbrick / Revive your Yureka or Yureka Plus 5510
RELAX & 100% UNBRICK / REVIVE Your Yureka/Yureka Plus 5510 here:-
I have successfully uploaded working 619Mb emmcBackup image.zip of Yureka /Yureka Plus 5510. Download it from*new link-
https://drive.google.com/file/d/1iiDMoc2inncw8oXkGTbS5Fu7DWLH2nOp/view?usp=drivesdk* .
Don't share this link(subject of YU T&C)
Unzip and then burn 12GB unzipped image file on your 16GB sd card using win image writer tool.*
After that follow xda / skyneel or gsmhost instructions to unbrick your device. .
Now you need all drivers and firmware.zip file that will work using QPST /qfil tool.
You can download firmware.zip from this link**
https://drive.google.com/file/d/1yxLxuzArcIwwZutuwd-4haiJ3nkf5vbH/view?usp=drivesdk*
It includes necessary firmware/flash file with working prog_emmc_firehose.mbn file to avoid sahara error,
QPST/Qfil tools and some partial drivers. .
Procedure Description:
It depends upon many factors that previously whether you have performed all the steps given on xda/other websites or not, Like Burning emmc image file of around 12GB on any 16/32GB memory card(use 16GB low cost sd card as it will get partially damaged permanently), Disassembling your bricked YU phone and make an arrangement for shorting pin no 2 and 4, Installing .Net Framework 4.0 and then QPST/Qfil Qualcomm flashing tool and several dependencies drivers like Qualcomm download mode driver 9008, HS-USB QDLoader 9008, USB Composite device 901, 15sec ADB driver/minimal ADB fastboot/Universal ADB driver, Coolpad driver for Qualcomm devices etc** If you have already performed all the above related steps and downloaded firmware.zip file for flashing via qfil and getting sahara error then I would like to share a small mbn programmer file only ( link*https://drive.google.com/file/d/1UwtrKQcfnthzzrwSwricNsVyfkzcjHlP/view?usp=drivesdk* ) So that you can copy this file to your firmware folder and next time while qfil flashing select my this file as programmer file to avoid sahara error.**
[SAHARA ERROR special help:
To avoid sahara fail error use proper prog_emmc_firehose.mbn provided by me in this post and immediately click on Download button of Qfil just after your PC detects in Qualcomm Download mode 9008.
Short pin 2 and 4 ,not 2 and 6 else your PC will start hanging.Though pin shorting strategy depends upon the type of hard bricking.]
However If you have not yet performed these steps as given on internet or If you have not been able to understand properly then send me your contact information like phone/email or place/location* so that I can provide you detail information or can help you physically. Thanks from Team xda.
Tried qfil for yu5510
it shows ERROR: bad magic:
Thanks for these method these one work for me for alive yureka plus [HARDBRICKED]
These way of flashing is work for me.....
around 1.5 year my phone will compltely dead till now and i tried many times. but no-one works for me but these fourm
and
1) Youtube link - youtube.com/watch?v=xgA8tTVV8RE
2) Youtube link - youtube.com/watch?v=XwK27aL2SKc
work for me
My phone has completely dead ( no fastboot, no Qualcomm driver show and no Notification ligth ) because i install custom rom many times
I follow these steps and Alive my phone again
Thank you so much :good::good:
Sorry for my bad english
My yureka plus dead after flash. Now it struck on yu logo.
Fastboot and recovery working. When flash any file uts shows remote write failed
.
EDIT: UPDATED March 6th, 2017 for March Google Security Updates Image
-------------------------------------------------------------------------
-------------------------------------------------------------------------
Stey-by-Step for Newbies Guide for restoring a bootloader-unlocked Pixel XL back to factory stock
This guide is ideal for soft-brick situations where you can't boot to your operating system​
***Verizon users should research before doing ANYTHING.
***Europe users should be researching before using North American images, though it's usually okay to do so.
SOFT BRICK vs. HARD BRICK:
-What is a hard brick? Well, if you cannot access your bootloader then you're probably hard-bricked and need to do a warranty repair.
-A soft brick is when you CAN access your boot loader. Because if you can access your boot loader then you can repair your own software issue by following this guide.
If your phone is soft bricked and you send it in for warranty then you're a twat.
BOOTLOADER:
How do I access my bootloader? Power off your phone. Hold down the power button and volume down button at the same time, for 20-40 seconds. If you just now shut down the phone, then it takes longer for the bootloader to come up. If the phone has been powered down at least 30 seconds then the bootloader should come up quicker. If your phone is stubbornly upset then it may take several tries and also holding down the two buttons for 40-60 seconds. Another thing that may prevent you from accessing the bootloader is a low battery of course. Never do any software trickery without at least a half full battery for multiple random reasons.
The directions below are for Windows 7 and may need to be modified for other OS's.
***Anyone who doesn't want to lose their setup/apps/user data, just edit the flash-all.bat to remove the -w from the script. Then it won't wipe anything.
You can use this modified flash-all.bat. It's for the latest March "B" image:
http://www.filedropper.com/flash-all_1
1) Install the Google Android driver if your Pixel XL isn't already recognized by your computer when booted to fastboot mode.
https://developer.android.com/studio/run/win-usb.html#download
2) Download the factory system image for Pixel XL (Marlin) to C:/Google
https://developers.google.com/android/images
---Here is the direct link for March "B - NOF27B" for All Other users (what we're using in this guide):
---https://dl.google.com/dl/android/aosp/marlin-nof27b-factory-2259c206.zip
---Here is the direct link for March "C - NOF27C" for Rogers users:
---https://dl.google.com/dl/android/aosp/marlin-nof27c-factory-b49c0e7b.zip
3) This is what the folder should look like after the download:
4) Now extract the file.
Your folder should look like this:
5) Go into the extracted folder:
6) The contents of the extracted folder should look like this:
7) Download Google's ADB/Fastboot files to this same folder:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
8) Now extract the ADB download to this same folder. Edit the path to look like it does below:
9) The folder should now look like this:
10) Go into that new folder and CUT all the contents:
11) Go up one folder and PASTE the files into the factory image folder:
12) The folder should now look like this:
13) Now boot your phone to Fastboot mode.
Power off the phone & disconnect from USB cable.
Wait 30 seconds.
Then press Power + Volume Down until you see this screen on your phone:
{
"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"
}
14) Now connect your phone to your computer via USB-C cable.
15) Wait 30 seconds.
16) Then double-click the ever famous "flash-all.bat" to restore your phone to stock.
17) You'll see a black command prompt window pup up and start restoring your phone to stock image.
It'll take 5-15 minutes and when completed, the output should look just like this, except for the "A" vs. "B" designations may be swapped around, and that's fine.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32976 KB)...
OKAY [ 0.876s]
writing 'bootloader_a'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_a"
(bootloader) Flashing active slot "_a"
OKAY [ 4.705s]
finished. total time: 5.583s
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio_a' (57192 KB)...
OKAY [ 1.457s]
writing 'radio_a'...
OKAY [ 0.562s]
finished. total time: 2.022s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.048s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1701181700
Baseband Version.....: 8996-012511-1701091826
Serial Number........: HT6920203793
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boot_a' (26173 KB)...
OKAY [ 0.690s]
writing 'boot_a'...
OKAY [ 0.299s]
erasing 'system_a'...
OKAY [ 0.265s]
sending sparse 'system_a' 1/4 (515613 KB)...
OKAY [ 13.636s]
writing 'system_a' 1/4...
OKAY [ 5.355s]
sending sparse 'system_a' 2/4 (514104 KB)...
OKAY [ 13.720s]
writing 'system_a' 2/4...
OKAY [ 6.234s]
sending sparse 'system_a' 3/4 (499613 KB)...
OKAY [ 13.263s]
writing 'system_a' 3/4...
OKAY [ 5.738s]
sending sparse 'system_a' 4/4 (32756 KB)...
OKAY [ 0.891s]
writing 'system_a' 4/4...
OKAY [ 0.359s]
erasing 'system_b'...
OKAY [ 0.297s]
sending sparse 'system_b' 1/4 (517080 KB)...
OKAY [ 13.672s]
writing 'system_b' 1/4...
OKAY [ 5.247s]
sending sparse 'system_b' 2/4 (514384 KB)...
OKAY [ 13.502s]
writing 'system_b' 2/4...
OKAY [ 10.252s]
sending sparse 'system_b' 3/4 (524287 KB)...
OKAY [ 13.766s]
writing 'system_b' 3/4...
OKAY [ 13.995s]
sending sparse 'system_b' 4/4 (85786 KB)...
OKAY [ 2.280s]
writing 'system_b' 4/4...
OKAY [ 2.969s]
erasing 'vendor_a'...
OKAY [ 0.250s]
sending 'vendor_a' (235322 KB)...
OKAY [ 6.049s]
writing 'vendor_a'...
OKAY [ 5.236s]
Setting current slot to 'a'...
OKAY [ 0.172s]
erasing 'userdata'...
OKAY [ 5.251s]
sending 'userdata' (138957 KB)...
OKAY [ 3.550s]
writing 'userdata'...
OKAY [ 1.298s]
rebooting...
finished. total time: 158.668s
Press any key to exit...
`
You're done.
There is no reason to continue reading this thread unless you want to "go the extra mile".
=================================
=================================
18) The phone automatically reboots at this point.
15) After it finished booting, I let it settle for five minutes.
16) I then reboot the phone (unnecessary step, just something I like to do).
17) I then log in and tell Google to restore my account from the cloud.
18) I set Display to stay on for 30 minutes so the phone doesn't go to sleep and my apps can restore without interruption.
19) After all apps are restored, I reboot and then update any remaining apps that need updates.
***OPTIONAL TIP*** Just prior to doing the flash-all.bat, it may not be a bad idea to make the additional step of flashing stock boot.img to both the A & B partitions.
Why not, right? This step is entirely optional and is only for good measure
Make sure you extracted the Google Image you downloaded, to the point where you find the boot.img and place it into the C:/Google folder.
The fastboot commands to install it are as follows:
Code:
fastboot flash boot_a boot.img
then...
Code:
fastboot flash boot_b boot.img
The output should look like this:
Code:
C:\Google>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (26229 KB)...
OKAY [ 0.718s]
writing 'boot_a'...
OKAY [ 0.296s]
finished. total time: 1.030s
C:\Google>fastboot flash boot_b boot.img
target reported max download size of 536870912 bytes
sending 'boot_b' (26229 KB)...
OKAY [ 0.718s]
writing 'boot_b'...
OKAY [ 0.265s]
finished. total time: 0.983s
C:\Google>
20) Boom, you're all done.
Either go find something else to do or continue reading this guide to root your phone, install TWRP and custom kernel.
=================================
=================================
*** MAY UPDATE USERS SEE THIS POST BEFORE GOING ANY FURTHER:
https://forum.xda-developers.com/showpost.php?p=72329767&postcount=176
TWRP, ROOT AND CUSTOM KERNEL INSTALL
****The next steps are only if you want to install TWRP, Root your phone and install ElementalX kernel.****
1) I enabled SystemUI Tuner (OPTIONAL).
2) I enabled Developer Options (OPTIONAL).
3) I enabled USB Debugging in Developer Options (OPTIONAL).
4) I enabled "Unknown Sources" in Security (OPTIONAL).
5) Download SuperSU root v2.79 SR3:
https://plus.google.com/+Chainfire/posts/27xToSqi5em
-----------Support thread for SuperSU
6a) Download TWRP RC1 IMG file:
https://dl.twrp.me/marlin/twrp-3.0.2-0-RC1-fastboot-marlin.img.html
6b) Download TWRP RC1 zip file:
https://dl.twrp.me/marlin/twrp-pixel-installer-marlin-3.0.2-0-RC1.zip.html
-----------Support thread for TWRP
7) Download ElementalX-P-1.07 kernel:
http://elementalx.org/devices/pixel/
-----------Support thread for ElementalX
8) Copy the TWRP, kernel and Root zip files to your Pixel's /sdcard (filenames in pic are outdated, sorry):
9) Copy TWRP's RC1 IMG file to C:/Google
10) Right-click any white spot in C:/Google and select the option to "Open Command Window Here"
11) Copy and paste the command "fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img".
The output should look like this after you press enter.
Code:
C:\Google>fastboot boot twrp-3.0
.2-0-RC1-fastboot-marlin.img
downloading 'boot.img'...
OKAY [ 0.710s]
booting...
OKAY [ 0.858s]
finished. total time: 1.578s
C:\Google>
The Pixel will automatically reboot to TWRP RC1 recovery.
12) Put a checkmark on the box "Never show this screen during boot again" and then swipe to allow modifications.
Click "Install".
Scroll down and click on the file named "twrp-pixel-installer-marlin-3.0.2-0-RC1.zip"
Swipe to confirm flash.
13) Reboot to Recovery.
14) Click the "Install" button.
15) Install the root file "SR3-SuperSU-v2.79-SR3-20170114223742.zip".
16) Reboot phone and verify root works. Do NOT install kernel yet. You need Superuser running first to gain ElementalX's advanced install options.
17) Now reboot to TWRP RC1 Recovery to install Kernel.
18) Install the kernel file "ElementalX-P-1.07.zip".
Go through the prompts to select your kernel options you want.
I recommend choosing the defaults unless you're a kernel expert who knows what to expect.
Now reboot normally.
Wait five minutes after bootup for the kernel to "settle".
Enjoy your modded Pixel XL!
=================================
=================================
TWRP BACKUP AND RESTORE
This section is if you installed TWRP and want to do a full ROM backup.
It's not as "obvious" on how to do this vs. older phones with TWRP.
The initial method is the same.
1) Boot to TWRP
2) Select the "Backup" option
3) Back up the "Boot", "System", "Vendor" and "Data". The Vendor option is important and may be new to some of you (it was to me).
If you want a "bit-for-bit" backup, then also select "System Image" and "Vendor Image". This will make your backup file size much larger than usual.
To restore, just do as normal.
Locate your backup and restore all items listed above.
I love this guide, but when I rebooted, it turns out I took the OTA, unintentionally and lost root. Any idea how I can block the OTA?
dablitzkrieg said:
I love this guide, but when I rebooted, it turns out I took the OTA, unintentionally and lost root. Any idea how I can block the OTA?
Click to expand...
Click to collapse
in developer settings....make sure automatic updates is not turned on
v2.2v said:
in developer settings....make sure automatic updates is not turned on
Click to expand...
Click to collapse
I'll try that and report back. Thanks
---------- Post added at 12:56 PM ---------- Previous post was at 12:21 PM ----------
v2.2v said:
in developer settings....make sure automatic updates is not turned on
Click to expand...
Click to collapse
I had that turned off and it still automatically pushed the update to X. How do I root now?
dablitzkrieg said:
I'll try that and report back. Thanks
---------- Post added at 12:56 PM ---------- Previous post was at 12:21 PM ----------
I had that turned off and it still automatically pushed the update to X. How do I root now?
Click to expand...
Click to collapse
Same method as before
Flash SuperSU in bootloader mode
Sent from my sailfish using XDA Labs
sd_shadow said:
Same method as before
Flash SuperSU in bootloader mode
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I'm on Verizon X. I am now stuck at the bouncing balls screen when I tried this suggestion. Any help would be appreciated.
dablitzkrieg said:
I'm on Verizon X. I am now stuck at the bouncing balls screen when I tried this suggestion. Any help would be appreciated.
Click to expand...
Click to collapse
There is lots of discussion about this in the SuperSU thread.
I'm not VZW so I can't help much, sorry.
maybe very stupid question ( and also very stupid from me to not look for it) but i dont know whitch version i have to select P, L or H. And cant watch it anymore Is there a way to find it out ?
Never mind i got it
---------- Post added at 10:51 PM ---------- Previous post was at 10:02 PM ----------
thanx for the great guide !!!!
dablitzkrieg said:
I'm on Verizon X. I am now stuck at the bouncing balls screen when I tried this suggestion. Any help would be appreciated.
Click to expand...
Click to collapse
WHat GB model do you have? flash-all flashed userdata, which cannot be flashed on 128GB model, I am searching for a manual way like the nexus 6P, flash each partition manually, in this thread, http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478 it shows the output and I think to do it manually must flash everything but userdata and do not format userdata if you want to keep internal memory in tact. I have seen some other guides, but they have not worked for me, because it is fastboot system system.img and I think it is fastboot system_a and fastboot system_b, like I said follow the commands and output
yung40oz84 said:
WHat GB model do you have? flash-all flashed userdata, which cannot be flashed on 128GB model, I am searching for a manual way like the nexus 6P, flash each partition manually, in this thread, http://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478 it shows the output and I think to do it manually must flash everything but userdata and do not format userdata if you want to keep internal memory in tact. I have seen some other guides, but they have not worked for me, because it is fastboot system system.img and I think it is fastboot system_a and fastboot system_b, like I said follow the commands and output
Click to expand...
Click to collapse
I am actually all set. Thx for the response though! It was simply an outdated adb/fastboot.
There is a possibility that Minimal ADB & Fastboot has some slightly older code buried in it so I recommend installing it, then updating the files using the link in step 2 just to be on the safe side.
Here's the link again. Thanks, Scott.
http://ul.to/6f5616c3
CZ Eddie said:
There is lots of discussion about this in the SuperSU thread.
I'm not VZW so I can't help much, sorry.
Click to expand...
Click to collapse
WHat GB model is yours? 128 or 32? I ask because previously on nexus 6P or older nexus devices you could not flash userdata on anything higher than 32GB model as it would only allocate 32GB on a 128Gb or 64GB model and mess internal size up. Also, this took you completely back to stock, like fresh out of the box setup, when I followed this manually it only was like an OTA, I still had my apps, data. etc.
yung40oz84 said:
WHat GB model is yours? 128 or 32? I ask because previously on nexus 6P or older nexus devices you could not flash userdata on anything higher than 32GB model as it would only allocate 32GB on a 128Gb or 64GB model and mess internal size up. Also, this took you completely back to stock, like fresh out of the box setup, when I followed this manually it only was like an OTA, I still had my apps, data. etc.
Click to expand...
Click to collapse
I'm 32GB.
But Google only offers one image and script for the 32 and 128.
CZ Eddie said:
I'm 32GB.
But Google only offers one image and script for the 32 and 128.
Click to expand...
Click to collapse
They only offer one image for the 6P and 5X as well regardless of memory size, but you still CANNOT flash userdata on a 64GB or 128GB 6P, it will leave you with only 32GB of space when booting up your phone, I know this for a fact, it is most likely the same for the Pixel and Pixel XL.
Note: You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Which I do not wipe internal memory anyway, but still cannot flash userdata for bigger storage models.
Can anyone other than yung40oz84 confirm that the flash-all.bat on a 128GB phone causes partition size issues?
CZ Eddie said:
Can anyone other than yung40oz84 confirm that the flash-all.bat on a 128GB phone causes partition size issues?
Click to expand...
Click to collapse
I used the flash all script on my 128gb version with no issues.
Thank God you fixed my Phone. I wanted to use the only rom out there and it killed my phone. Thank you for a clear instruction on how to restore my phone! Wish every one would be a little more clear.
Ok have a issue. When I run flash-all.bat I get waiting on device. Phone is already in bootloader mode. And device is recognized by adb.
moosc said:
Ok have a issue. When I run flash-all.bat I get waiting on device. Phone is already in bootloader mode. And device is recognized by adb.
Click to expand...
Click to collapse
It's clearly a lack of communication issue.
Wrong driver?
Are you sure you're in Bootloader and not in Recovery?
Recovery uses ADB and Bootloader uses fastboot.
Yeah I'm in bootloader. Also redid USB drivers. Tried using skip soft it rebooted into bootloader then hung up on waiting for any device
CZ Eddie said:
It's clearly a lack of communication issue.
Wrong driver?
Are you sure you're in Bootloader and not in Recovery?
Recovery uses ADB and Bootloader uses fastboot.
Click to expand...
Click to collapse
The old kernels were 4.4.78 - but in the latest ColorOS 6 (based on Android 9 instead of 8) I noticed the kernel is now 4.4.153 - not far behind the very latest commit at the time of writing (193) - but has the source code been published anywhere??? Perhaps we can find that kernel source under a different Realme device. I could then have a go at turning on virtualization again via the built-in KVM kernel module (enabled through make menuconfig just prior to compilation).
The kernel is dated August 24th - so would that make it newer than Firmware version A21? The firmware is named up as RMX1807EX_11_C.24 or RMX1801EX_11_OTA_0240
I've uploaded it here in normal ZIP format if you need it. You can flash it with the latest TWRP or R2X2:
https://eu.dl.twrp.me/RMX1801/
https://forum.xda-developers.com/realme-2-pro/development/stable-r2x2-recovery-t3899121
If you've already unlocked the bootloader: just reboot and hold volume DOWN to get to Fastboot and plug into a Windows 10 PC via USB:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.3.1-1-RMX1801.img
target reported max download size of 536870912 bytes
sending 'recovery' (24412 KB)...
OKAY [ 0.524s]
writing 'recovery'...
OKAY [ 0.110s]
finished. total time: 0.637s
OR
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery R2X2.img
target reported max download size of 536870912 bytes
sending 'recovery' (25165 KB)...
OKAY [ 0.560s]
writing 'recovery'...
OKAY [ 0.120s]
finished. total time: 0.684s
Copy RMX1801EX_11_OTA_0240_all_HRfI3IQiI3cB.zip to disk along with Magisk-v19.3.zip. Boot into Recovery, wipe everything except Internal storage and the last 2-3 under cache, and then click on Install to flash each ZIP file in turn.
The problem for me though: I'm not then able to install @SamarV-121's LineageOS 16 nor LinegageOS 15 anymore - even after installing the old vendor.img! And for some reason I have to keep manually mounting the data partition for files to appear in recovery. Lastly, I have a different "bootloader unlocked" screen during fastboot (might that be a secure boot screen that could be turned off?). At one point my Wifi even stopped working - so not sure what's going!? But everything seems stable right now under ColorOS 6 - still unlocked and rooted - except for that flashing message in red at the top of the screen "Rooting of your phone.... Tap to fix...".