Develop Bugs

downgrade htc desire HD

Hallo guys
i followed this article
http://forum.xda-developers.com/showthread.php?t=905003
but i have problem see the picture
http://tinypic.com/view.php?pic=2drfbko&s=7
software number
1.83.415.4
sorry for my bad English
thanks for the help

Hala!
thats because its not 'adb push psneuter /date/local/tmp'
its adb push psneuter /data/local/tmp
not date -- its data

Lmao we've all made that mistake at least once

its a typo!!.. like me in the first time.

thanx guys for reply
i just laughed at myself

cant get the "#" in the result
i do as this
Section 2b [For Gingerbread ROMs, 2.x]
•Connect Desire HD to a computer. Charge only, USB Debugging enabled!
•Open up a cmd and go to Downgrade folder, execute commands:
Code:
adb push misc_version /data/local/tmp
adb push fre3vo /data/local/tmp
adb shell chmod 777 /data/local/tmp/fre3vo
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
./data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF
i am on HTC Desire Hd
androin 2,3,3
htc sense 2,1
kernel 2,6,35,10
versio 2,50,405,2
If you got "#" in the result, you have temporary root! Proceed with commands:
Code:
cd /data/local/tmp
./misc_version -s 1.31.405.6
but i dont Get the "#"

Yeah the only # i get in my results is "fre3vo by #teamwin following the results.. so i just try to type the 2nd to last command "cd /data/local/tmp i get "path not specified" ?
but the last thing the results say is "running exploit" then waiting for my next command???

I am also trying to downgrade. I get the same meesages as @mistage1990
C:\Documents and Settings\Administrator\Skrivebord\htc\Downgrade_v3\Downgrade>ad
b shell
$ ./data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF
./data/local/tmp/fre3vo -debug -start FBB00000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 106
width: 62
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region fbb00000...
Potential exploit area found at address fbb7f800:1800.
Exploiting device...
C:\Documents and Settings\Administrator\Skrivebord\htcDowngrade_v3\Downgrade>cd
/data/local/tmp
system can not find path
What do i do next? i have tried to search, but i do not exatly what to search for

Same problem as above
Hey all,
I'm getting exactly the same error as ko1979 above. Does anyone know if there's a solution to this yet?

[Q] Downgrade from 2.50.405.2

Hi people.
I realize that the usual response to threads like this is "read the forum" but I honestly have, I've tried several guides but I get no luck.
So if anyone would please help me out, it would be much appreciated and maybe helpful for others.
The way I've understood things is that I need to
1. Temproot
2. Downgrade using a goldcard.
Using this guide
HTML:
http://forum.xda-developers.com/showthread.php?t=1152233
I think I've managed to temp root;
1. Temproot:
C:\DHDDowngrade>root
C:\DHDDowngrade>adb push fre3vo /data/local/tmp
1195 KB/s (9796 bytes in 0.008s)
C:\DHDDowngrade>adb shell chmod 777 /data/local/tmp/fre3vo
C:\DHDDowngrade>adb shell /data/local/tmp/fre3vo -debug -start FBB00000 -end FFF
FFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 800
bits_per_pixel: 32
activate: 16
height: 106
width: 62
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region fbb00000...
Potential exploit area found at address fbb7f800:1800.
Exploiting device...​
I do get kicked back to the command prompt, but if I type "adb shell" I do get the "#" that I'm supposed to be getting.
Right - so far so good, right?
2. Downgrade
As instructed in the guide, I run the commands as follows
C:\DHDDowngrade>adb push misc_version /data/local/tmp
1288 KB/s (15837 bytes in 0.012s)
C:\DHDDowngrade>adb shell chmod 777 /data/local/tmp/misc_version
C:\DHDDowngrade>adb shell /data/local/tmp/misc_version -s 1.31.405.3
--set_version set. VERSION will be changed to: 1.31.405.3
Patching and backing up partition 17...
Error opening input file.
C:\DHDDowngrade>adb reboot bootloader​
There is an error here, but I haven't found anyone else having this problem, and don't even know if it really is a problem.
So I've ignored it, and continued on creating a coldcard.
I've tried using Goldcard manager from the market, I've tried retrieving the reverse CID manually. I've pasted the data from the generated image file onto the card and saved. A few times I've not been able to paste PD98IMG.zip on to the card afterwards, giving me the error that the card must be formatted to work, but lastly it would let me copy. If I try reading the card, I do get the error that the card has to be formatted. My HTC also tells me theres something wrong with the SD card. I've ignored this, and booted into the bootmanager. For a split second theres a green text saying something i along the lines of "PD98IMG image not found".
And so it ends, I can't get any further.
So the questions summarized are;
1.Is this the correct order?
2.Am I rooted, even if I have to type "adb shell" to get the "#"?
3.When dowgrading, is the "Error opening input file" fatal?
4.Is the card supposed to be unreadable after pasting the hex data onto it?
Sorry for the neverending post, but getting a custom rom onto my Desire HD has been very, very hard. Unsuccesful so far. Please help me out
Best regards from Norway.

Hi there noticed no one has replied I have plenty of time to help you out the best I can. I recently did this last week and had no problems. Im still learning myself so sorry if i am not the best of help.
wow long post
After skimming your post I did notice something. I pretty sure that you need to create a gold card first. If you still have problems creating a GoldCard get back to me but here is the link:
http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
I then followed this tutorial to downgrade:
http://forum.xda-developers.com/showthread.php?t=905003
and then use the s-off tool :
http://forum.xda-developers.com/showthread.php?t=857537
hope that helps, get back to me if you need help.

I used these two guides when rooting my DHD, I also had to use a goldcard but the link for that is in the downgrade page below.
1. Downgrade
http://forum.xda-developers.com/showthread.php?t=905003
2. Root + Radio installation + Rom installation
http://forum.xda-developers.com/showthread.php?p=11557769
As far as I know, the two links above are the correct order, as long as you get the # its safe to proceed and the card should be usable after you make it into a goldcard, at least I still use mine. Oh, and you shouldn't receive any errors throughout the process, it might not be fatal but why take a chance.

ace hack kit
use the ace hack kit to steps you can't get wrong
http://www.google.com/url?sa=t&sour...sg=AFQjCNFFmKIBniFFp-RmQV7lN2Ma-n9dzQ&cad=rja

TheJokah said:
use the ace hack kit to steps you can't get wrong
http://www.google.com/url?sa=t&sour...sg=AFQjCNFFmKIBniFFp-RmQV7lN2Ma-n9dzQ&cad=rja
Click to expand...
Click to collapse
Thanks to all of you for replying.
My head was spinning after going through different tutorials and problem solutions - and I had frankly given up the whole thing.
But TheJokaH's one-click method seemed intriguing so I decided to give this one.last.shot. And it worked!
I don't know why this isn't posted as the only sticky thread at the Q&A section - because is definitely the only way to get one started with custom roms.
Thanks again!

[Q] Clockwork recovery freeze on charge

I can turn ON my phone when is charge at power OFF.
When i flash my phone with shipped rom this problem disapear.
This all is started with PC49IMG.zip which containt recovery.img Clockwork 3.0.0.6
I know the clockwork has nothink to do with this. But there is bad config somewhere.
Android OS wont shutdown after unplug charger.
1. Phone is OFF
2. Plug in Charger
3. Led turn into red/green
4. Unplug charger (led not turn off)
5. Phone cant be turn on into system
2. Plug in Charger
6. adb devices
List of devices attached
HT0BHPY***** recovery
7. uname -a
Linux localhost 2.6.32.21-HCDRJacob-g606a571 #1 PREEMPT Wed Jan 26 18:29:52 GMT
2011 armv6l GNU/Linux
8.mount
Code:
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)
9. ps
Code:
PID USER VSZ STAT COMMAND
1 root 244 S /init
2 root 0 SW [kthreadd]
3 root 0 SW [ksoftirqd/0]
4 root 0 SW [watchdog/0]
5 root 0 SW [events/0]
6 root 0 SW [khelper]
7 root 0 SW [kinteractive_up]
8 root 0 SW [knteractive_dow]
9 root 0 SW [async/mgr]
10 root 0 SW [suspend]
11 root 0 SW [sync_supers]
12 root 0 SW [bdi-default]
13 root 0 SW [kblockd/0]
14 root 0 SW [kmmcd]
15 root 0 SW [bluetooth]
16 root 0 SW [smd_tty]
17 root 0 SW [qmi]
18 root 0 DW [rpcrouter]
19 root 0 SW [krpcserversd]
20 root 0 SW [microp_work_q]
21 root 0 SW [button/0]
22 root 0 SW [detect/0]
23 root 0 SW [button/0]
24 root 0 SW [detect/0]
25 root 0 SW [khungtaskd]
26 root 0 SW [kswapd0]
27 root 0 SW [aio/0]
28 root 0 SW [crypto/0]
43 root 0 SW [kadspd]
44 root 0 SW [panel_on/0]
45 root 0 SW [msm_serial_hs]
46 root 0 SW [msm_serial_hs]
47 root 0 SW [mtdblockd]
54 root 0 SW [rmnet/0]
55 root 0 SW [msm_hsusb]
56 root 0 SW [usb_mass_storag]
57 root 0 SW [gs_tty]
58 root 0 SW [atmel_wq]
59 root 0 SW [ls_wq/0]
60 root 0 SW [curcial_wq]
61 root 0 SW [kstriped]
62 root 0 SW [kondemand/0]
63 root 0 SW [binder]
64 root 0 SW< [krfcommd]
65 root 240 S /sbin/ueventd
66 root 0 SW [sd-qd]
67 root 6152 S /sbin/recovery
68 root 3364 S /sbin/adbd recovery
101 root 0 SW [flush-31:0]
102 root 1604 S /sbin/sh -
122 root 1592 R ps
10.cat init.rc
Code:
on early-init
start ueventd
on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard
symlink /system/etc /etc
mkdir /boot
mkdir /sdcard
mkdir /sd-ext
mkdir /datadata
mkdir /emmc
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs
on boot
ifup lo
hostname localhost
domainname localdomain
class_start default
service ueventd /sbin/ueventd
critical
service recovery /sbin/recovery
service adbd /sbin/adbd recovery
disabled
on property:persist.service.adb.enable=1
start adbd
on property:persist.service.adb.enable=0
stop adbd
11. cat default.prop
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRG83
ro.build.display.id=GRH78C
ro.build.version.incremental=eng.koush.20110218.153840
ro.build.version.sdk=9
ro.build.version.codename=REL
ro.build.version.release=2.3.2
ro.build.date=Fri Feb 18 15:38:58 PST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-OSx86.local
ro.build.tags=test-keys
ro.product.model=HTC Wildfire
ro.product.brand=htc_wwe
ro.product.name=cyanogen_buzz
ro.product.device=buzz
ro.product.board=buzz
ro.product.cpu.abi=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=buzz
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=passion-user 2.2.1 FRG83 60505 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/rel
ase-keys
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.media.dec.jpeg.memcap=10000000
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.vmail.23415=1571,BT
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=8
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.def.agps.mode=2
wifi.interface=eth0
wifi.supplicant_scan_interval=45
ro.sf.lcd_density=120
view.fading_edge_length=8
view.touch_slop=15
view.minimum_fling_velocity=25
view.scroll_friction=0.008
ro.secure=0
ro.tether.denied=false
ro.telephony.default_network=0
ro.opengles.version=65536
media.stagefright.enable-record=true
dalvik.vm.execution-mode=int:fast
ro.com.google.locationfeatures=1
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.rommanager.developerid=cyanogenmod
ro.url.legal=
ro.url.legal.android_privacy=
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,113,115,117,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
ro.modversion=CyanogenMod-7.0.0-RC1-buzz-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Its called offmode charging bug, it is caused by clockwork and a simple search would've found your solution to this.
Either live with it like the rest of us using 3.0.0.6 or upgrade to one of the latest versions of clockwork which supposedly fix it.
Sent from my HTC Wildfire using xda premium

Simple battery pull and turn on after if you want to charge whilst off. Or just charge whilst in screen off,I was too like you wanting to charge when off but I live with it now and to be honest my phone is never turned off anyway so I've gone back to cwm 2.5 just because I'm used to the layout and I'm green crazy lol.
sent from my wilderbeast/buzz

So CWM 2.5.0.1 can be booted without removing batery with keys:
power+vol_dwn+track_ball
I Get from market Rom Manager.
It wont upgrade my recovery.
But look like it upgrade.

mertuarez said:
So CWM 2.5.0.1 can be booted without removing batery with keys:
power+vol_dwn+track_ball
I Get from market Rom Manager.
It wont upgrade my recovery.
But look like it upgrade.
Click to expand...
Click to collapse
All Clockworkmod Recoveries with the Offmode Charging Bug can be started using the 3 keys, as you have described above.
ROM Manager's Clockworkmod Recoveries are temporary, as they are stored on your SDCArd, and can be accessed only when you Select 'Reboot into Recovery' from within ROM Manager. Your primary Clockworkmod Recovery remains untouched.
To permanently upgrade your Clockworkmod Recovery, you are going to have to flash the Recovery IMG File. Details here:
http://forum.xda-developers.com/showpost.php?p=12782368&postcount=2
(Refer the part 'Custom Recoveries' and 'How to install a new Clockworkmod Recovery Image')

[SOLVED]
It's all i need.
I did't know that all CWM have Three Combo to shutdown.
I have lots of troubles for this because before then i reflash with shipped rom my HTC_ BUZZ eat too much power. So now it stay up even 3-4days (idle) .
And it's very unconfortly to remove battery all time.
I cant believe how shortly people react here
Really thanks so much.

mertuarez said:
[SOLVED]
It's all i need.
I did't know that all CWM have Three Combo to shutdown.
I have lots of troubles for this because before then i reflash with shipped rom my HTC_ BUZZ eat too much power. So now it stay up even 3-4days (idle) .
And it's very unconfortly to remove battery all time.
I cant believe how shortly people react here
Really thanks so much.
Click to expand...
Click to collapse
3xeno (yoda) is always on the ball, i dont think he sleeps. lol

I wondering how it's possible but with CWM v5.0.2.0 from 3xeno link my phone will works fine for now. When is offmode and i pull out charge it will shutdown led will turn off. Even when is charging it goes to power ON.
So i make backups.
Incredibble, wonderfull, amazing, exciting.
ps: I do some changes but that has notting to do with it.
Upgrade SU,Busybox

[Q] /efs backup

Hello. I need help with backing up my /efs folder. I tried different methods and none seemed to work.
Phone: GT-S5660 Gio
Network Lock [OFF]
Network Subset Lock [OFF]
SP Lock [OFF]
CP Lock [OFF]
Android: 2.3.3
PDA : S5660XXKPO
PHONE : S5660XXKPA
CSC : S5660OXFKP5
Lurking the forums I tried different methods with no luck:
C:\sdk>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ su
su
# tar zcvf /sdcard/efs-backup.tar.gz /efs
tar zcvf /sdcard/efs-backup.tar.gz /efs
tar: not found
# exit
exit
$ exit
exit
=======================
C:\sdk>adb shell
$ su
su
# busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
tar: /efs: No such file or directory
tar: error exit delayed from previous errors
# cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
/dev/block/stl3: Invalid argument
# exit
exit
$ exit
exit
This method creates efs_dev-block-stl3.img (0 bytes) and efs-backup.tar.gz (29 bytes)
=======================
EFS Pro
Checking Device Connection... Device Connected!
Restarting ADB Server... Okay!
Checking ROOT Access... Device Has ROOT Permissions!
Backing Up Device's '/efs' Folder, Please Wait...
Creating EFS Backup TAR Archive... EFS Backup Failed!
Operation Finished!
With the ISO option the program freezes.
=======================
C:\sdk>adb shell
$ su
su
# dd if=/dev/block/stl4 of=/sdcard/efs.rfs
dd if=/dev/block/stl4 of=/sdcard/efs.rfs
/dev/block/stl4: cannot open for read: Invalid argument
# exit
exit
$ exit
exit
=======================
I also tried this:
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=u
tf8 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.sportstracklive.stopwatch-1 vfat ro,dirsync,nosuid
,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859
-1,shortname=mixed,utf8,errors=remount-ro 0 0
$
=======================
With Root Explorer I am unable to find the /efs
Sorry for the long post, but what am I missing?
Best regards, V a L y O.

STOP!
The first rule with the Gio is not to mess with the EFS partition if you don't know what you're doing.
It is located in stl5, but you very much risk corrupting it solely by mounting and reading it.
Corruption in this case means a bricked phone or a blank IMEI, which means no phone service.
Either backup bml5, or work in recovery mode.

Thank you for the replay.
I know that messing with the stl5 can brick the phone. Well, that already happened once when I used Odin to flash a wrong 2.3.5 version. Lucky for me, It was repaired under warranty.
That's why I want to make a backup to the system files.
bml5 is backed up. Is it enough to fix the phone in case I brick it again?
Best regards, V a L y O.

now my phone have blank imei
but, i still can use it for sms, call & internet
is anyone here know how to restore it?
lucky, in indonesian imei is not requirement for gettiong mobile service service

phiexz said:
now my phone have blank imei
but, i still can use it for sms, call & internet
is anyone here know how to restore it?
lucky, in indonesian imei is not requirement for gettiong mobile service service
Click to expand...
Click to collapse
Same here! I live in the Netherlands and also have a blank IMEI(IMEI is 000000000000) but still evrything works except swype install because it requires an IMEI number. Somebody know how to fix it? maybe to use somebody elses IMEI? with /efs restore or is there an way to import my own IMEI in somebody elses /efs backup?

Help with building Ubuntu Touch for the 1+3

Hello guys,
Because i love Ubuntu i am willing to try to build Ubuntu Touch for the 1+3.
I installed "phablet-dev-bootstrap" and when i try to run it it just hangs... :crying:
Code:
[email protected]:~/Desktop$ mkdir phablet
[email protected]:~/Desktop$ phablet-dev-bootstrap phablet/
INFO:phablet-dev-bootstrap:Changing to workdir /home/youri/Desktop/phablet
INFO:phablet-dev-bootstrap:Initializing repository
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
Get https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 2399 100 2399 0 0 7513 0 --:--:-- --:--:-- --:--:-- 7513
Invalid clone.bundle file; ignoring.
And after waiting for like 2 minutes i got the following error..
Code:
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503 Service Unavailable
fatal: The remote end hung up unexpectedly
What goes wrong? I could not find anything related on the internet...

same issue here .
i have been checking other forum too , \
and i found a chat on stack-exchange 15 day old than today ,
this happened because server hosting files ran out of storage or something ,
and some important files got deleted , they restored those files some of them were able to sync but
problem is back again , i am writing this wondering if there is a way around
i cant post links to the chat as its my first
sorry if there is any grammar mistakes , or spell mistakes