Develop Bugs

Problem in kernel Arc S

Kernel when flashing the device does not work, but when entering Hotbot mode it works
(Kernel does not work I have)
My Phone Is Xperia Arc S
http://www.youtube.com/watch?v=1U0kBrHz3xQ&feature=youtu.be

What exactly You need? If You want to flash new kernel, try with QuickIMG.

darkknightma said:
Kernel when flashing the device does not work, but when entering Hotbot mode it works
Click to expand...
Click to collapse
Use the right command. fastboot flash boot kernel.img

XperienceD said:
Use the right command. fastboot flash boot kernel.img
Click to expand...
Click to collapse
I used the right command but kernel not working

What happens when you type this command? CMD should show something like this:
Code:
C:\Users\dfharhdh\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
oot boot.img
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 9198kB/s
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.139s]
finished. total time: 1.775s
Remember to rename kernel file to "boot.img" and run CMD with administrator rights.

pypcier said:
What happens when you type this command? CMD should show something like this:
Code:
C:\Users\dfharhdh\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
oot boot.img
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 9198kB/s
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.139s]
finished. total time: 1.775s
Remember to rename kernel file to "boot.img" and run CMD with administrator rights.
Click to expand...
Click to collapse
Lol was just about to post something and you beat me to it
And make sure the kernel img is in firmware folder of flashtool you where flashing it from your desktop folder

tallman43 said:
Lol was just about to post something and you beat me to it
And make sure the kernel img is in firmware folder of flashtool you where flashing it from your desktop folder
Click to expand...
Click to collapse
You seem pretty competent when it comes to fastboot so can you help me with something? Every time i want to flash a new kernel after opening CMD I have to change directory to a folder containing boot.img and its pretty frustrating for me. Is there a folder for img files so fastboot will find them automatically? I've thought about creating a shortcut so CMD will open in right directory automatically but I'm lazy.

pypcier said:
You look pretty competent when it comes to fastboot so can you help me with something? Every time i want to flash a new kernel after opening CMD I have to change directory to a folder containing boot.img and its pretty frustrating for me. Is there a folder for img files so fastboot will find them automatically? I've thought about creating a shortcut so CMD will open in right directory automatically but I'm lazy.
Click to expand...
Click to collapse
To be 100 % honest not sure!I know in windows you can change default opening behavior of directories to open to your favorite folder etc,I once did ita long time ago but forgot how to
But what your suggesting sounds like a good idea:good: yep me lazy too don't use cmd much to be honest I use Doomlord's toolbox lol

So it looks like a customized shortcut is my only option. I like fastboot because its simple and reliable also typing stuff in black window is always cool. Life on the edge *****es!

pypcier said:
So it looks like a customized shortcut is my only option.
Click to expand...
Click to collapse
"Shift + Right Click" opens a command window in whatever folder you are in.
---------- Post added at 05:38 PM ---------- Previous post was at 05:34 PM ----------
darkknightma said:
I used the right command but kernel not working
Click to expand...
Click to collapse
If it hot boots then it should flashboot and usually doesn't because People use the wrong command.

ALT + Right Click" opens a command window in whatever folder you are in.
Click to expand...
Click to collapse
Not on windows 8. I could do a shift + right click combo for "open cmd here" but this is useless because fastboot needs to be running with administrator rights. To be honest I don't care anymore because I've made a shortcut for opening cmd in a right folder with admin rights and even fancy blue font (*****es love blue fonts).

pypcier said:
What happens when you type this command? CMD should show something like this:
Code:
C:\Users\dfharhdh\AppData\Local\Android\android-sdk\platform-tools>fastboot flash b
oot boot.img
sending 'boot' (5632 KB)...
(bootloader) USB download speed was 9198kB/s
OKAY [ 0.634s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.139s]
finished. total time: 1.775s
Remember to rename kernel file to "boot.img" and run CMD with administrator rights.
Click to expand...
Click to collapse
this image when I flash kernel in fastboot but not working
{
"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"
}

Its pretty bad :c you have a bad block in your kernel "partition" and its preventing you flashing kernels. As far as I know this can't be fixed. You can't flash custom kernels I'm sorry :<
edit
It's a physical error in a memory chip in your phone. After searching for more info I think there is nothing you can do.

[Q] SG Gio (GT-5660) - Wireless & Bluetooth won't work

Hy guys!
I have this phone: Samsung Galaxy Gio (GT-S5660).
I got the phone from a friend, with this pecs:
- Model number: GT-S5660
- Android version: 2.3.6
- I don't know: Baseband version, Kernel version and Build number. Sorry!
I can make phone calls, but i can't send messages (also, when i make a call, it asks me if i want to call "Korea or Another country"). If this helps, on the back cover is a "Olleh" logo (this one).
So i decided to flash a new ROM. First of all, I installed CWM 5.0.2.7.
Then i tried this ROMs:
A. From Maclaw (Here):
1. Ice Cream Sandwich 4.0.4 (AOSP) final 1 - [full_gio-ota-eng.final1.zip]
2. Ice Cream Sandwich 4.0.4 (CyanogenMod 9) final 1 - [cm_gio-ota-eng.final1.zip]
3. Jellybean 4.2.2 (AOSP) beta1 - [full_gio-jellybean.beta1.zip]
B. From MoltenMotherBoard (this Thread)
1. AOSP IceCreamSandwich 4.0.4 | RC4 | - [aosp-ics_4.0.4_RC4_MMB.zip]
C. From sammobile.com
1. S5660XXKTK_S5660OXFKT4_CNX.zip - [this one]
All of them had the same problem: No WIFI & No Bluetooth.
Please help me fix this problem. I'm awake since yesterday trying to fix the phone.
Thanks!

your phone is not gts5660,it is shw-m290k,the Korean version of Gio and it has different hardware
To fix this problem,you need to back to m290k stock ROM
The Chinese are improving themselves!

czkwg8 said:
...you need to back to m290k stock ROM
Click to expand...
Click to collapse
Thanks for the info!
And where can i find that?

for m290k firmware go to this site
www.sammobile.com/forum/showthread.php?t=8468
Sent from my SHW-M190S using Tapatalk 2

First of all, thanks czkwg8 for finding the file!
I did this:
1. I downloaded the ROM.
2. Then i reboot the phone into recovery.
3. Wiped data (factory reset) + Wipe Cache.
4. Shutdown the phone & Enter in Download mode.
5. Then i opened Oddin Multi Downloader v4.42.
6. Clicked on "OPS" button, selected the "GIO_v1.0.ops" file.
7. Checked the "One Package" box.
8. Clicked on "One Package" button and selected the "SHW-M290K-GIO-HOME-TH25-REV03-user.tar" file.
9. Connected the USB cable & Clicked "Start" button in Oddin.
Then i received this Message in Oddin:
Code:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
<1> 1/8 Finished.
<1> qcsbl download..
<1> 2/8 Finished.
<1> oemsbl download..
<1> 3/8 Finished.
<1> amss download..
<1> 4/8 Finished.
<1> arm11boot download..
<1> 5/8 Finished.
<1> boot.img download..
<1> 6/8 Finished.
<1> recovery.img download..
<1> 7/8 Finished.
<1> system.rfs download..
<1> 8/8 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
Now the phone is showing the "Olleh" logo over and over again.
It's stuck in bootloader or something?
What do i have to do?

3agl3deejay said:
First of all, thanks czkwg8 for finding the file!
I did this:
1. I downloaded the ROM.
2. Then i reboot the phone into recovery.
3. Wiped data (factory reset) + Wipe Cache.
4. Shutdown the phone & Enter in Download mode.
5. Then i opened Oddin Multi Downloader v4.42.
6. Clicked on "OPS" button, selected the "GIO_v1.0.ops" file.
7. Checked the "One Package" box.
8. Clicked on "One Package" button and selected the "SHW-M290K-GIO-HOME-TH25-REV03-user.tar" file.
9. Connected the USB cable & Clicked "Start" button in Oddin.
Then i received this Message in Oddin:
Code:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
<1> 1/8 Finished.
<1> qcsbl download..
<1> 2/8 Finished.
<1> oemsbl download..
<1> 3/8 Finished.
<1> amss download..
<1> 4/8 Finished.
<1> arm11boot download..
<1> 5/8 Finished.
<1> boot.img download..
<1> 6/8 Finished.
<1> recovery.img download..
<1> 7/8 Finished.
<1> system.rfs download..
<1> 8/8 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
Now the phone is showing the "Olleh" logo over and over again.
It's stuck in bootloader or something?
What do i have to do?
Click to expand...
Click to collapse
boot to recovery then do a full wipe.
Sent from my SHW-M190S using Tapatalk 2

czkwg8 said:
boot to recovery then do a full wipe.
Click to expand...
Click to collapse
I did that. Same problem.

3agl3deejay said:
I did that. Same problem.
Click to expand...
Click to collapse
have you done a wipe after Flash the stock ROM with Odin?
Sent from my SHW-M190S using Tapatalk 2

czkwg8 said:
have you done a wipe after Flash the stock ROM with Odin?
Click to expand...
Click to collapse
What types of data wipe am i suppose to do after flashing the Stock ROM with Oddin? And in what order?
1. Wipe data / factory reset
2. Wipe Cache partition
3. Wipe Dalvik Cache

3agl3deejay said:
What types of data wipe am i suppose to do after flashing the Stock ROM with Oddin? And in what order?
1. Wipe data / factory reset
2. Wipe Cache partition
3. Wipe Dalvik Cache
Click to expand...
Click to collapse
"Wipe data / factory reset" is the only one you need to do.

thanks for good info

Solved!
Finaly... works!
I did this:
1. Wipe data / factory reset (in CWM)
2. Wipe Cache partition (in CWM)
3. Wipe Dalvik Cache (in CWM)
4. Flash Stock Firmware (with Oddin, without checking the "Auto Reboot" box)
5. Wiped all data / cache (in 'Stock' Recovery)
6. Reboot system
7. Works perfect!
Thanks czkwg8 fot all the help!

3agl3deejay said:
Finaly... works!
I did this:
1. Wipe data / factory reset (in CWM)
2. Wipe Cache partition (in CWM)
3. Wipe Dalvik Cache (in CWM)
4. Flash Stock Firmware (with Oddin, without checking the "Auto Reboot" box)
5. Wiped all data / cache (in 'Stock' Recovery)
6. Reboot system
7. Works perfect!
Thanks czkwg8 fot all the help!
Click to expand...
Click to collapse
you only need to do the follow steps:
1.flash stock ROM with Odin
2.boot to stock recovery(3e recovery) and do a factory reset(wipe data&cache)
Sent from my SHW-M190S using Tapatalk 2

czkwg8 said:
you only need to do the follow steps:
1.flash stock ROM with Odin
2.boot to stock recovery(3e recovery) and do a factory reset(wipe data&cache)
Sent from my SHW-M190S using Tapatalk 2
Click to expand...
Click to collapse
i solved my problem this metod--
1.flash m290s to 5660
many files (boot, pda, modem, csc) attention - not one package
may be you - wipe data.
you phone must be work, but no work wifi and bluetooth.
2. flash original rom m290s may be you - wipe data. and ENJOY.
p.s. sorry my bad english. good luck

krysakg said:
i solved my problem this metod--
1.flash m290s to 5660
many files (boot, pda, modem, csc) attention - not one package
may be you - wipe data.
you phone must be work, but no work wifi and bluetooth.
2. flash original rom m290s may be you - wipe data. and ENJOY.
p.s. sorry my bad english. good luck
Click to expand...
Click to collapse
i have no m290k,my phone now is m190s(galaxy s hoppin)
m290k has different wifi and Bluetooth hardware
The Chinese are improving themselves!

S5660 Using Odin Multiloader to root using Version 6 of CWM
I had a 'soft brick' when attempting to update my rooted jellybean on my S5660 from the SD Card.
Following very helpful advice on XDA, I was able to restore factory settings -- back to 2.3.6 -- using Odin Multiloader (from my Samsung laptop) and the relevant files in download mode.
I then rooted successfully using Odin Multiloader to load version 5 of CWM.
However, I understand if I want to install Cyanogenmod KitKat, I need to update CWM to version 6.
When I attempted this from the SD Card, it failed, i.e. I could launch the operating system but could not access the root.
I have read and attempted to press all three buttons as advised elsewhsyntaxere on XDA but without success.
Can I root version 6 using a .tar file and Odin, as I did successfully with version 5?
If so, is there a link for the zip file?

Solved
After some deep research on this excellent forum I have managed to install kitkat on my S5660.

boot loop after factory reset

Basicly my gio is stuck on boot loop
ived tryed a lot of flashing roms with Odin.
My gio can enter download mode but cant enter recovery mode.
Can some one help me please
i would be apreciated
ived started this thread but someone said that the place to be is in the development section so...
http://forum.xda-developers.com/showthread.php?p=40806190#post40806190

Delete this thread bro

Andrea19 said:
Delete this thread bro
Click to expand...
Click to collapse
Ty Bro ,thats really the help i need. :good:

mnunes01 said:
Ty Bro ,thats really the help i need. :good:
Click to expand...
Click to collapse
It's an GENERAL thread thing. It's not that hard to know I think... development thread is for things you develop. Ask a moderator to move it. If everyone place his problems and questions in the dev sections...
Sent from my GT-5660 using xda premium

hi man, which rom and which recovery was you using when you did that factory reset?

ro_bo said:
hi man, which rom and which recovery was you using when you did that factory reset?
Click to expand...
Click to collapse
i think it was on the 2.2.1 the recovery i dont really know.
FlemishDroid i know you're rigth, but man, you really remember my boss talking about putting hours into the redmine....
anyway and since you're rigth my thread is:
http://forum.xda-developers.com/show...0#post40806190

mnunes01 said:
i think it was on the 2.2.1 the recovery i dont really know.
FlemishDroid i know you're rigth, but man, you really remember my boss talking about putting hours into the redmine....
anyway and since you're rigth my thread is:
http://forum.xda-developers.com/show...0#post40806190
Click to expand...
Click to collapse
Try flashing 2.3.6 and don't select auto reboot in odin and i don't think that CWM v5.x.x.x works on 2.2

CataHd said:
Try flashing 2.3.6 and don't select auto reboot in odin and i don't think that CWM v5.x.x.x works on 2.2
Click to expand...
Click to collapse
One stupid question, do i need to have the microsd inserted to flash or enter recovery mode ?

mnunes01 said:
One stupid question, do i need to have the microsd inserted to flash or enter recovery mode ?
Click to expand...
Click to collapse
I think you need sdcard because CWM saves some files there but i don't really know because i never used my phone without sdcard

CataHd said:
I think you need sdcard because CWM saves some files there but i don't really know because i never used my phone without sdcard
Click to expand...
Click to collapse
try'd everithing I could imagine, flashed 2.3.6, 2.3.5, 2.3.3, always boot loop
flashed 2.2.1 odin still recognizes the phone on usb connecting, but screen went completely black thoug i had brick the phone that time but still can enter donwloading mode. flahsed again 2.3.3 and boot loop again.
Iam starting to think that it was something to do with ext4 and rfs, maybe some partitions went bad...
Any clue?
I would really apreciate a recovery mode screen....

Download firmware from (is 2.3.6, January 2013) here (link 1)
Use ODIN from here (link 2)
To enter download mode hold volume-down button + home then turn on the phone.
Open ODIN press OPS button and point Odin to the OPS file from the archive from link 2
Check "One package" then press One Package button and point Odin to the file from link 1
Click Start and wait, I don't know what can go wrong now - I never really understand how people can brick their phones, I personally flashed today Froyo, then got back to ICS!
Remember! If you flash Froyo and you want to come back to Gingerbread/ICS/CM/etc., first flash a 2.3.5/2.3.6 rom! Only after flashing 2.3.5/2.3.6 you can flash CWM recovery and install your custom ROM

bgm92 said:
Download firmware from (is 2.3.6, January 2013) here (link 1)
Use ODIN from here (link 2)
To enter download mode hold volume-down button + home then turn on the phone.
Open ODIN press OPS button and point Odin to the OPS file from the archive from link 2
Check "One package" then press One Package button and point Odin to the file from link 1
Click Start and wait, I don't know what can go wrong now - I never really understand how people can brick their phones, I personally flashed today Froyo, then got back to ICS!
Remember! If you flash Froyo and you want to come back to Gingerbread/ICS/CM/etc., first flash a 2.3.5/2.3.6 rom! Only after flashing 2.3.5/2.3.6 you can flash CWM recovery and install your custom ROM
Click to expand...
Click to collapse
ty for the response. I'ved tryied that, but still in bootloop... i really think i got a corrupeted partitions or something...
anyway theres is the odin log:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
<1> 1/9 Finished.
<1> qcsbl download..
<1> 2/9 Finished.
<1> oemsbl download..
<1> 3/9 Finished.
<1> amss download..
<1> 4/9 Finished.
<1> arm11boot download..
<1> 5/9 Finished.
<1> boot.img download..
<1> 6/9 Finished.
<1> recovery.img download..
<1> 7/9 Finished.
<1> system.rfs download..
<1> 8/9 Finished.
<1> csc.rfs download..
<1> 9/9 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
when it gets to hte reset pda, the phone just starts blinking the screen and never reboot

man try erase your sd with cm and then try put a good rom on the sd when the sd is on another phone...than do a full wipe (not to the sd)
and flash-it on your phone...i think these will work...
soory for my bad englesh

FyJy said:
man try erase your sd with cm and then try put a good rom on the sd when the sd is on another phone...than do a full wipe (not to the sd)
and flash-it on your phone...i think these will work...
soory for my bad englesh
Click to expand...
Click to collapse
But didn i need to have acess to recovery mode on my phone to do that?

i had the same problem as you
what i did was disconnect the phone from usb and take out the battery
then i entered recovery and factory reset
and it worked
i flashed 2.3.6 for my country, find out what firmware you need and flash only that

Try flashing recovery.img manually using fastboot, then reboot to recovery (via fastboot)

[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016]

PERISIST ERROR IN TWRP WHILE FLASHING ANY ZIP.....? THEN HERE IS THE GUIDE
{
"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"
}
I am not responsible for anything that may happen to your phone as a result of installing custom roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
What is the persist partition?
Persist is partition mounted at /persist. It has ext4 file system. DRM releated files, sensor reg file (sns.reg), wifi and bluetooth mac addresses are stored there.
If you experience the following issues:
1. You get "e: cannot mount /persist" in recovery
2. Can't access to internal storage.
3. Boot loop on Lollipop 5.0 and above
4. IMEI number is lost even after formating cache and fastboot flash cache.img
5. No signal even after formating cache and fastboot flash cache.img
Then your persist partition have to be fixed​
Follow instructions carefully to solve this issue
NOTE : UNLOCK your device bootloader first before doing this
1. Download this " persist file & ADB+&+Fastboot of yureka " provided by @Annabathina
2. extract them in PC
3. open ADB+&+Fastboot of yureka
4. place presist.img file which you have extracted in ADB+&+Fastboot folder
5. Hold shift key and right click on mouse and select Open command window here
6. Connect your device to pc..... and make sure that drivers are installed properly..... ( VERY VERY IMPORTANT )
a. Type : adb devices
If your device is connected you will get it in connected devices list
b. Type : adb reboot-bootloader
Your phone will restart into bootloader.
c. Type : fastboot -i 0x1ebf flash persist persist.img
7. Disconnect your device from PC and REBOOT​
ADB+&+Fastboot : link
persist : link
Useful links
ADB for pc : link
YU usb drivers : link
PdaNet drivers : link
@Annabathina............................for Guide
Ricks ............... for Presist file
YU YUREKA
YU YUREKA PLUS​
XDA:DevDB Information
[Guide] Persist error fix in YUREKA / PLUS [21-Apr-2016], Tool/Utility for the YU Yureka
Contributors
Annabathina
Version Information
Status: Stable
Stable Release Date: 2016-04-21
Created 2016-04-21
Last Updated 2016-04-23

Reserved

Reserved

I dont get a multirom function in the advanced settings menu. Is it because im using twrp 3.0.... Or is it bcoz of persist partition ?
Sent from my AO5510 using XDA-Developers mobile app

After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..

Bazilbycom said:
After booting into fastboot mode .. i put the commands and then it just says "waiting for device"..
Click to expand...
Click to collapse
Have you solved it?

saurav007 said:
Have you solved it?
Click to expand...
Click to collapse
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers

Hi,
For me the message is : is not possible to erase this partition
Thanks a lot for your help

still same error.....what to do now..??

Bazilbycom said:
Yes! .. All you have to do is install proper drivers for your device .
Use PDAnet and Google Usb Drivers
Click to expand...
Click to collapse
Earlier i was getting error even after installing all the drivers, all i needed was to update PDAnet on phone as well & it does everything.
Thank you it worked well!

still stucking
i was suffering of problem error persist but using this method it solved the error is gone but not still my device stuck on boot i tried many custom roms stock rom formats and all but still it stuck after 2 of android logo. in twrp recovery in mount option the system, persist, firmware are uncheck .i think it means they are not mount right??? i click many time to check and reboot but still logo stuck problem please give me solution!!!!!!!
Thank You

Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk

vijaysingh1996 said:
Can I flash this zip by twrp
Sent from my YU5510 using Tapatalk
Click to expand...
Click to collapse
This isn't TWRP flashable zip. You have to flash via fastboot (see OP) after extracting the img from downloaded zip file.

Failing on my Pantech Sky Vega Iron 2 IM-A910S (codename: ef63) and bootloader unlocked.
In Fedora Linux the command continues to display "waiting for device" message even though the device is detected by "fastboot devices" command, although its serial number is not displayed and ???????? is display in that place.
While in Windows 7 (64-bit), the following error message is displayed after execution of the command "fastboot -i 0x1ebf flash persist persist.img":
target reported max download size of 1610612736 bytes
sending 'persist' (4324 KB)...
OKAY [ 0.165s]
writing 'persist'...
FAILED (remote: It is not surpport in user build.)
finished. total time: 0.186s
Any one please help...

In my device it showing can't load persist
After typing last line

shekarsahani said:
In my device it showing can't load persist
After typing last line
Click to expand...
Click to collapse
Can you post CMD screenshot?
Make sure the file name is same as in CMD.

Unfortunately I can't is send cmd screenshot it is not uploading..
When I type fastboot -i 0x1ebf flash persist persist.img then it shows error cannot load 'persist.img'

Lineage installation on nexus 7 (2013) flo error

Hi all,
when installing Lineage 18.1 on my Nexus 7 (2013) flo, i keep getting this ERROR: 1
i figured i must be missing something, so i wiped everything and re-uploaded the image to the internal storage over usb.
unfortunatly this keeps happening
any help would be much appreciated
{
"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"
}

basdejongg said:
Hi all,
when installing Lineage 18.1 on my Nexus 7 (2013) flo, i keep getting this ERROR: 1
i figured i must be missing something, so i wiped everything and re-uploaded the image to the internal storage over usb.
unfortunatly this keeps happening
any help would be much appreciated
Click to expand...
Click to collapse
Hi, let's see...
Code:
Transferring: 449987627/449987627 (100%)
3263 KB/s (449987627 bytes in 134.671s)
Wait...
Installing zip file '/tmp/lineage-18.1-20210306-UNOFFICIAL-flo.zip'
Checking for Digest file...
Unmounting System...
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 1
Error installing zip file '/tmp/lineage-18.1-20210306-UNOFFICIAL-flo.zip'
Done processing script file
You're right. Let's remedy this situation with sysrepart-ultimate.zip...
Code:
Transferring: 174140/174140 (100%)
3627 KB/s (174140 bytes in 0.046s)
Wait...
Installing zip file '/tmp/sysrepart-ultimate.zip
Checking for Digest file...
Unmounting System...
##########################################
# k23m Nexus 7'13 Repartition [ultimate] #
##########################################
Creating log
Removing partitions
Creating new partitions
Formatting new partitions
#######################
# Operation completed #
# REBOOT NOW! #
#######################
Done processing script file
...and re-try...
Code:
Transferring: 449987627/449987627 (100%)
3168 KB/s (449987627 bytes in 138.671s)
Wait...
Installing zip file '/tmp/lineage-18.1-20210306-UNOFFICIAL-flo.zip'
Checking for Digest file...
Unmounting System...
Target: google/razor/flo:6.0.1/MOB30X/3036618:user/release-keys
Patching system image unconditionally...
script succeeded: result was [1.000000]
Done processing script file
All OK

Thanks @k23m for the sysrepart, i used TWRG to run that and it did work fine.
now the nexus keep booting in fastboot mode and i cannot install TWRG again to install the lineage.zip
fastboot flash recovery .\twrp-3.5.2_9-0-flo.img
sending 'recovery' (10060 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.026s

basdejongg said:
fastboot flash recovery .\twrp-3.5.2_9-0-flo.img
sending 'recovery' (10060 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.026s
Click to expand...
Click to collapse
"FAILED (data transfer failure (Unknown error))" is actually a known error of bad USB cables as you can read eg here.
Incidentally, you could install everything automatically in one go with CROSS.

thanks! now i get the message that the file size is to big
Code:
.\twrp-3.5.2_9-0-flo.img
sending 'recovery' (10060 KB)...
OKAY [ 0.337s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 0.378s

any idea @k23m ?

basdejongg said:
any idea @k23m ?
Click to expand...
Click to collapse
Yes, already suggested in CROSS...
"If direct sysrepart installation is impossible due to TWRP or GPT issues, run the repartition.bat script."
"If you see errors, copy and report them. Run getlog.bat and include "getlog.log" in your post. If possible, also run relog.bat and attach "relog-xxxxxx.zip" to your post."
"CROSS works on PC with Windows, or WinPE if you do not have Windows installed." (or in VirtualBox)